"Daniel J. Sinder" <[EMAIL PROTECTED]> writes:
> This is much clearer to me, for one, and I see how the need can
> arise. But it appears somewhat redundant in that you could always
> re-organize your file to achieve the same effect (at the cost of a
> deeper hierarchy).
Fair enough -- i may try
Bastien wrote:
> "Egli Christian (KIRO 43)" <[EMAIL PROTECTED]> writes:
>
>>> **: a headline
>>> It would be convenient when you need to store inline tasks that are
>>> neither proper headlines nor list items. Such a headline wouldn't
>>> (un)fold, not because its content must stay invisible, bu
"Egli Christian (KIRO 43)" <[EMAIL PROTECTED]> writes:
>> **: a headline
>
>> It would be convenient when you need to store inline tasks that are
>> neither proper headlines nor list items. Such a headline wouldn't
>> (un)fold, not because its content must stay invisible, but because it
>> has n
Hi all
> Maybe not directly related, but still: what about my past suggestion
> of a static (unfoldable) but active headline?
> The syntax i suggested for it was like:
> **: a headline
> It would be convenient when you need to store inline tasks that are
> neither proper headlines nor list i
Leo <[EMAIL PROTECTED]> writes:
>>> For example, if I set "#+ARCHIVE: ::* Archived Tasks" and ARCHIVE tag
>>> "* Archived Tasks", then future archiving (org-archive-subtree) will
>>> create another "* Archived Tasks". Is this intended?
>>
>> I have fixed this bug for 4.66. Is there then still nee
On 2007-02-18, Carsten Dominik said:
> On Feb 11, 2007, at 11:37, Leo wrote:
>
>> On 2007-02-11, Carsten Dominik said:
>>
>>> Why don't you "misuse" the ARCHIVE tag for this? You could change
>>> the name of the tag to LOCK or something? Or maybe we could have a
>>> list of tags that causes this
On Feb 11, 2007, at 11:37, Leo wrote:
On 2007-02-11, Carsten Dominik said:
Why don't you "misuse" the ARCHIVE tag for this? You could change
the name of the tag to LOCK or something? Or maybe we could have a
list of tags that causes this behavior.
For example, if I set "#+ARCHIVE: ::* Arc
On 2007-02-11, Carsten Dominik said:
> Why don't you "misuse" the ARCHIVE tag for this? You could change
> the name of the tag to LOCK or something? Or maybe we could have a
> list of tags that causes this behavior.
For example, if I set "#+ARCHIVE: ::* Archived Tasks" and ARCHIVE tag
"* Archiv
