From: Steven Lumos <steven@lumos.us>
To: emacs-orgmode@gnu.org
Subject: Re: blorg.el
Date: Wed, 20 Feb 2008 16:44:01 -0800 [thread overview]
Message-ID: <x6lk5ft9ym.fsf@bitty.lumos.us> (raw)
In-Reply-To: 87k5l1um5d.fsf@bzg.ath.cx
Bastien Guerry <Bastien.Guerry@ens.fr> writes:
> Rick Moynihan <rick@calicojack.co.uk> writes:
>
>> But the problem appears to be that the URL which appears twice in the
>> block isn't inserted literally but is instead expanded into an <a
>> href=""> in the source when M-x blorg-publish is run e.g:
>>
>> <object width="425" height="355"><param name="movie" value="<a
>> href="http://www.youtube.com/watch?v=fu8rAWciQNs"">watch?v=fu8rAWciQNs"</a>></param><param
>> name="wmode"
>> value="transparent"></param><embed src="<a
>> href="http://www.youtube.com/watch?v=fu8rAWciQNs"">watch?v=fu8rAWciQNs"</a>
>
> Argh. I see.
>
>> Is there a way to disable this when inside dynamic blocks?
>
> Not one that I will work on now. But please be patient, I'm coding the
> new export engine and it will be much easier to publish a blog with it.
>
> --
> Bastien
Just FYI, I'm out here trying to remain patient too. The general
methodology of blorg seems to be just about exactly how I would prefer
to blog, and I'm especially interested in the handling of source
examples with htmlize that was previously mentioned.
Steve
next prev parent reply other threads:[~2008-02-21 0:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 11:44 blorg.el Dimitris Kapetanakis
2008-01-29 15:18 ` blorg.el bzg
2008-01-29 15:09 ` blorg.el Rick Moynihan
2008-01-29 15:54 ` blorg.el Dimitris Kapetanakis
2008-01-30 6:59 ` blorg.el Bastien Guerry
2008-02-19 10:18 ` blorg.el Rick Moynihan
2008-02-19 13:10 ` blorg.el Bastien Guerry
2008-02-21 0:44 ` Steven Lumos [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-30 5:25 blorg.el Dimitris Kapetanakis
2008-01-30 6:29 ` blorg.el Bastien Guerry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x6lk5ft9ym.fsf@bitty.lumos.us \
--to=steven@lumos.us \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).