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.
Hmmm, I guess you still want these to contribute to sparse trees and
the agenda ?
- Carsten
On Feb 10, 2007, at
Hello Carsten,
In org, if a subtree has a ARCHIVE tag, it will stay collapsed in
visibility cycling. I found this functionality useful in two cases:
- When archive location is in the same file as .org file
- A tree with REPEATing items.
Thus, I suggest if a heading of a subtree starts with '
