From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Minimal overhead Org-mode blogging system
Date: Sun, 17 Jun 2012 10:09:23 +0200 [thread overview]
Message-ID: <2012-06-17T10-02-37@devnull.Karl-Voit.at> (raw)
In-Reply-To: loom.20120513T164916-349@post.gmane.org
Sorry for the late reply. I was off the mailing list for one and a
half month. Therefore I include a full quote.
* Neil Smithline <emacs-orgmode@neilsmithline.com> wrote:
>
> Karl Voit <devnull <at> Karl-Voit.at> writes:
>> Therefore I sat down and thought about a workflow that should be
>> enough for writing simple weblog entries:
>>
>> - create an Org-mode heading (anywhere!)
>> - make sure that there is an (uniq) :ID: property
>> - add the tag :blog: to heading
>> - <write content, subheadings, ...>
>> - change state of top-heading to DONE
>> - this enables blog entries «in the queue»
>> - (manually) invoke generation-script
>>
>> This enables me quick blogging with a list of advantages:
>>
>> - a blog entry can be located anywhere in all of my Orgmode files
>> - no extra formatting steps
>> - very small (almost non-existent) overhead to create a blog entry
>> - no duplicate information
>> - updates only in Orgmode, not HTML or any in-between format
>> - static (fast) pages
>> - self-hosting without any fancy services behind like RDBS
>> Karl,
>
> I'm wondering if you've played around with this at all? I happen to really like
> the idea but I wonder about its performance.
I am writing my PhD thesis these days and therefore I do not have
time for this blogging thing until November or January :-(
Performance is no issue at all on *my* side. I plan to re-generate
the whole blog every night using a cron job.
But I do understand your concern when you need something which is
updaten instantly. (Not my personal requirement.)
> Unless I'm mistaken, and I very likely may be, won't you have to scan all of
> your .org files to look for the special tags/properties/todo states/whatever?
Yes. I plan to scan each (or a defined subset) of my Org-mode files.
> If not, I'd love to have a pointer to how you can accomplish this without
> scanning every .org file. That would be cool.
Sorry.
But anyhow: whatever I hack, it will be on github [1] and everybody
is free to fork and add a better performing real-time update
mechanism. I also have a cool name for my project - be curious *g*
1. https://github.com/novoid/
--
Karl Voit
prev parent reply other threads:[~2012-06-17 8:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 16:51 Minimal overhead Org-mode blogging system Karl Voit
2011-12-07 16:30 ` Steinar Bang
2011-12-07 17:20 ` Puneeth Chaganti
2011-12-07 20:11 ` Eric Schulte
2011-12-11 13:20 ` Bastien
2011-12-08 0:31 ` Karl Voit
2011-12-08 4:29 ` Puneeth Chaganti
2011-12-08 14:19 ` Karl Voit
2011-12-08 16:45 ` Puneeth Chaganti
2011-12-08 22:02 ` Karl Voit
2012-01-15 18:08 ` Steinar Bang
2012-01-16 22:54 ` Puneeth Chaganti
2012-01-19 22:15 ` Steinar Bang
2012-01-20 18:19 ` Chris Gray
2012-01-21 5:15 ` Scott Randby
2012-01-21 5:53 ` Nick Dokos
2012-01-21 6:26 ` Chris Gray
2012-01-17 18:50 ` tychoish
2012-01-18 3:06 ` Eric Schulte
2012-01-20 16:10 ` Bastien
2012-02-11 13:47 ` François Pinard
2011-12-11 4:33 ` Nathan Neff
2012-05-13 14:54 ` Neil Smithline
2012-05-15 2:24 ` Jude DaShiell
2012-05-16 0:48 ` Neil Smithline
2012-05-16 9:51 ` Jude DaShiell
2012-05-20 21:48 ` Neil Smithline
2012-06-17 8:09 ` Karl Voit [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=2012-06-17T10-02-37@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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).