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 keeping the sparse-tree "filter" applied. But I guess it doesn't make much sense. Well, I guess I could leave it as a suggestion for new functionality, but I don't even know if it's feasible. Thanks! On Sun, Feb 26, 2023 at 8:52 AM Ihor Radchenko <yanta...@posteo.net> wrote: > > Cassio Koshikumo <ckoshik...@gmail.com> 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. Now, put point on heading One and press TAB. Child is > > hidden. > > > > The problem: press TAB again. Now Two and Three are also shown, > > effectively breaking the sparse tree filtering. (Actually Five is > > shown, too, it seems...) > > <TAB> is not affected by sparse tree. > Sparse tree just reveals headings that match certain criteria and > highlights them. > > May you describe what you expected to happen? > > -- > Ihor Radchenko // yantar92, > Org mode contributor, > Learn more about Org mode at <https://orgmode.org/>. > Support Org development at <https://liberapay.com/org-mode>, > or support my work at <https://liberapay.com/yantar92> -- Cassio Koshikumo