Cassio Koshikumo writes:
> Hm. It makes sense that TAB is not affected... Somehow I hadn't really
> considered that.
>
> What I expected to happen (and now I realize it was not a justified
> expectation) was to have the visibility of the sparse-tree kept while
> tabbing. So I could expand a tree,
Hm. It makes sense that TAB is not affected... Somehow I hadn't really
considered that.
What I expected to happen (and now I realize it was not a justified
expectation) was to have the visibility of the sparse-tree kept while
tabbing. So I could expand a tree, then collapse it again, all the
while
Cassio Koshikumo writes:
> Create an .org file with the following contents:
>
> * First Level
> ...
> Now, C-c / m (or M-x org-sparse-tree and select m) and Match: tag.
>
> The resulting sparse tree looks like this:
>
> * First Level
> ** One :tag:
> *** Child
> ** Four :tag:
>
> So far, so good.
I don't know if this can be considered a bug or if I'm trying to do
something not supported.
Create an .org file with the following contents:
* First Level
** One :tag:
*** Child
** Two
** Three
** Four :tag:
** Five
Now, C-c / m (or M-x org-sparse-tree and select m) and Match: tag.
The resulti
