From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: A Blorg/org based blog
Date: Sun, 14 Oct 2007 22:30:59 +0100 [thread overview]
Message-ID: <87r6jxxu24.fsf@bzg.ath.cx> (raw)
In-Reply-To: <e85471e30710141225p35154cbnca9c6a53e78c9bca@mail.gmail.com> (Rick's message of "Sun, 14 Oct 2007 20:25:43 +0100")
Hi Rick,
Rick <rick.moynihan@gmail.com> writes:
> I don't find writing such things easy, so I'm happy to be using
> blorg/org/emacs which don't seem to interfere as much with the
> creative flow as logging into a wordpress/blogger account can.
>
> http://sourcesmouth.co.uk/blog/
Glad to see this!
> First impressions are that Blorg seems to work quite well, though it
> takes some setting up, and could be made more flexible
Sure. I wrote blorg more than one year ago, and I made the mistake of
trying too add too many functions too early.
Since that time, Org changed a lot and introduced properties - blorg
should be able to take advantage of them somehow. Also, some code I
wrote in org-export-latex.el could be of some help in parsing the Org
file to get it published as a blog.
My plan is to rewrite blorg nearly from scratch, trying not to rush on
functionnalities and adding them only if people need them.
> sometimes seems to be a little temperamental in publishing to html
> with links not rendering properly etc
The next version of blorg will use Org internals for rendering HTML.
The good thing of all this is that, no matter how far blorg1 will be
from blorg0, you can always work on your Org source without worrying
too much on this! Source is source :)
Thanks for trying blorg, happy orging,
--
Bastien
next prev parent reply other threads:[~2007-10-14 20:31 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 [this message]
2007-10-16 21:38 ` Rick
2007-10-17 1:22 ` Bastien
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=87r6jxxu24.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).