[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Minimal overhead Org-mode blogging system
From: |
Jude DaShiell |
Subject: |
Re: [O] Minimal overhead Org-mode blogging system |
Date: |
Wed, 16 May 2012 05:51:33 -0400 (EDT) |
I don't know enough lisp to implement this indexing system. On Tue, 15
May 2012, Neil Smithline wrote:
> I like your indexing idea. I use a less-complex system involving symbolic
> links for my agenda files. Yours sounds better.
>
> This is what I use for my agendas:
>
> (setq org-agenda-files
> (list (expand-file-name "~/Documents/+OrgAgendas")))
>
> (defun org-add-agenda-file ()
> (interactive)
> (make-symbolic-link (buffer-file-name) "~/Documents/+OrgAgendas"))
>
> It is just a quick-and-dirty solution. If I remove or move a file, I get
> errors. Also, if I stop using a file for agenda items I must manually unlink
> the symlink.
>
> Have you implemented your indexing system Jude or just designed it? I'd love
> to see it if you have something working. I imagine it could be used for todos,
> cross-referencing tags, properties, etc...
>
> And to prevent Carsten from yelling at me :-D, I would insist that, by
> default, Emacs would not create the cross-referencing database. You'd have to
> explicitly enable it.
>
> Neil
>
> On Mon May 14 22:24:08 2012, Jude DaShiell wrote:
> > Understand, I use update here in the sense of some file modification
> > that subsequently gets saved. If files to be modified get archived into
> > org-mode's revision control system, the blog tag and associated done tag
> > could be searched for within the save process and an org database could
> > build with file name and then tripplets of date stamp, line number for
> > blog tag, line number for done tag and each tripplet would hold another
> > blog entry in that unique file which is the first field in the data
> > base. So you want to find a blog entry? Search the org-generated data
> > base for a date stamp and you come up with the file and the range of
> > line numbers holding that blog entry. Search one file and go to
> > specific location in second file. That if it's done or gets done will
> > keep file searching to a nice minimum permanently.
> >
> > On Sun, 13 May 2012, Neil Smithline 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.
> > >
> > > 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?
> > >
> > > If not, I'd love to have a pointer to how you can accomplish this without
> > > scanning every .org file. That would be cool.
> > >
> > >
> > >
> >
> > ----------------------------------------------------------------
> > Jude <jdashiel-at-shellworld-dot-net>
> > <http://www.shellworld.net/~jdashiel/nj.html>
> >
>
>
----------------------------------------------------------------
Jude <jdashiel-at-shellworld-dot-net>
<http://www.shellworld.net/~jdashiel/nj.html>