From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: A Blorg/org based blog
Date: Wed, 17 Oct 2007 02:22:21 +0100 [thread overview]
Message-ID: <87ir56fsc2.fsf@bzg.ath.cx> (raw)
In-Reply-To: <e85471e30710161438xae8da99v91ce604e2c29e748@mail.gmail.com> (Rick's message of "Tue, 16 Oct 2007 22:38:32 +0100")
Rick <rick.moynihan@gmail.com> writes:
> Yes it's a good strategy and one that's worked well for org-mode. I
> do however have some features which I'd like to see. If it's not too
> rude, I'll list some here:
>
> - Ability to define your own HTML <head>'s. Specifically here the
> issue was wanting to list a 3rd party feed (feedburner) rather than
> my own as a <link> in the <head>. I did in fact modify blorg.el to do
> this through a new customize variable. If you want I can send you the
> patch.
Please do!
> - Ability to include code blocks in posts (with syntax highlighting).
I've just discovered the htmlize-output-type variable (letting some
htmlized code to be embedded in other HTML documents), so it should
be possible.
> - The ability to make an image a link i.e. to output <a href="..."><img ...></a>
> - To allow sorting of published posts by their date rather than their
> order in the org-mode file.
> - To have more customizable echoes.
Agreed.
> I also noticed that my templates tended to be practically identical,
> causing a lot of duplicated code between them.
Yes, some re-factorization needed here.
> Being able to include your own elisp in these templates would also be
> handy. Also writing/copying&pasting HTML inside customize buffers is
> a little painful.
Mhh.. true.
Thanks for the feedback!
--
Bastien
prev parent reply other threads:[~2007-10-17 0:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 19:25 A Blorg/org based blog Rick
2007-10-14 21:30 ` Bastien
2007-10-16 21:38 ` Rick
2007-10-17 1:22 ` Bastien [this message]
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=87ir56fsc2.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).