Hello Ian,
I just read the docs and I like it so far. There are three things I’d
mention:
• Some finders have missing documentation (although their names are pretty
straightforward)
• Why the “new language”, why can’t it be lisp, or at least more lispish?
• You gave us a possibility to create
I've been working on something akin to org-depend.el called org-edna.
Basically, Edna provides an extensible means of specifying blocking
conditions and trigger actions.
For example, Edna allows you to specify that a task should be blocked
until all TODOs have been addressed in source code:
*
"Loris Bennett" writes:
> "Loris Bennett" writes:
>
>> "Loris Bennett" writes:
>>
>>> Hi,
>>>
>>> I'm interested in exporting from Org to Foswiki format. Is
>>> org-export-generic.el still the way to go or has
Stefan Kredler writes:
> when archiving sections or exclude them from export I would expect
> them being exempt from being evaluated during export.
> The section archived or marked as ~:no export:~ is still evaluated and there
> is an error
> if the reference in the include
"Loris Bennett" writes:
> "Loris Bennett" writes:
>
>> Hi,
>>
>> I'm interested in exporting from Org to Foswiki format. Is
>> org-export-generic.el still the way to go or has this been superseded by
>> something else?
>
> Nevermind, I
Nicolas Goaziou writes:
> I disagree. You may want to cancel the message because this change
> doesn't require one, but, yet, want the todo state change.
I see, that makes sense.
I notice that supplying an empty message with C-c C-k results in no
logbook entry at all. Is that intended behaviour
when archiving sections or exclude them from export I would expect
them being exempt from being evaluated during export.
The section archived or marked as ~:no export:~ is still evaluated and there is
an error
if the reference in the include file is no longer available. I get the error
message
Hello,
Joe Corneli writes:
> The (xxx) form for a link target, especially one outside of a block,
> doesn't seem to have meaning within the document model that Org
> understands.
Of course it does. It belongs to the link syntax. See, for example
`org-link-search'