[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Using orgmode to take "inline notes" for research

From: John Hendy
Subject: Re: [O] Using orgmode to take "inline notes" for research
Date: Wed, 6 Apr 2011 13:08:47 -0500

On Wed, Apr 6, 2011 at 12:27 PM, Samuel Wales <address@hidden> wrote:
> Hi John,
> They only solve half of the problem.
> Unbreakable bidirectional links using ID markers would solve
> the teleport problem.  Both ends can be moved anyplace,
> including inside stretches of text.  They are a little like
> a generalization of footnotes.  They use org IDs.  You can
> specify various things for export and appearance in the org
> buffer and so on.  ID markers are a proposal in the list
> archives; they can be used for graph-theoretic applications.
> Bidirectional links are simply a pair of ID markers that are
> made to act as links also and that point to each other.

This sounds very cool. I can't gather from the mailing list thread
(which appears to be just you) whether this is implemented or just
suggested. Is it possible to actually use this or not?

> However, you still need to figure out how to put notes at
> the top.  I wonder if inline tasks can work for this.  Maybe
> you can put a tag on each to specify that it is a note, then
> somehow export notes first, then everything except notes.
> I'm note sure how to design that to fit into org nicely.
> Maybe there is some way to do this:
>  * Here is my whole document (by inclusion)
>    (some kind of syntax here to say insert all :note: headlines)
>    Here are the things the notes refer to.  You can
>    teleport to them.
>    (some kind of syntax here to say insert all other headlines)

This would be pretty neat.

> Babel has something similar, but I don't know if it can do
> it.  I have long wanted a way to include the body of a
> headline upon export (maybe it is possible now, dunno) and
> this is a generalization that lets you include all headlines
> with a certain tag or all headlines without it.
> We would want it to be useful for more purposes.  Perhaps
> Extensible (i.e. universal) Syntax would allow flexibility here.
> It would prevent having to invent new syntax, because the
> same syntax is used for other features according to the car.

Agreed -- it would be neat to have the syntax/tools available to use
it for whatever, and as a result of such a feature set, it could be
used for this.

Thanks for sharing,

>  * Here is my whole document (by inclusion)
>    $[include :headlines-from-elisp (org-tags-view nil ":note:")]
>    Here are the things the notes refer to.  You can
>    teleport to them.
>    $[include :not-headlines-from-elisp (org-tags-view nil ":note:")]
> Samuel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]