From: Meir Goldenberg <mgoldenbe@gmail.com>
To: Meir Goldenberg <mgoldenbe@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: A bug with expanding headlines of the sparse tree?
Date: Wed, 12 Aug 2015 11:25:43 +0300 [thread overview]
Message-ID: <CAP1Du3VeiqHMZ0mxNdgPsFzV6L+dDxzXS1eu8_kUVSC6+H8M9w@mail.gmail.com> (raw)
In-Reply-To: <87si7p77tg.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
Is there an alternative to TAB when I want to work only with the sparse
tree and all the other entries only distract me? If not, can I somehow open
the sparse tree in a separate buffer?
On Wed, Aug 12, 2015 at 1:56 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Meir Goldenberg <mgoldenbe@gmail.com> writes:
>
> > I do not quite understand. You wrote: "TAB discloses the entry and all
> > children. It also leaves the entry in an editable state." However, Task2
> is
> > not a child of the entry being disclosed (Task1).
>
> I explained why hiding Task2 leaves entry in an uncomfortable state,
> where you could edit near ellipsis.
>
> > Furthermore, by constructing the sparse tree, I am telling org-mode
> > that I am only interested to see the sub-trees under the tasks marked
> > as TODO!
>
> TAB ignores you want to keep a sparse tree. Note that it is also used to
> get out of parse trees, i.e., get a normal view again.
>
>
> Regards,
>
[-- Attachment #2: Type: text/html, Size: 1427 bytes --]
next prev parent reply other threads:[~2015-08-12 8:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 12:49 A bug with expanding headlines of the sparse tree? Meir Goldenberg
2015-08-11 13:07 ` Nicolas Goaziou
2015-08-11 19:16 ` Meir Goldenberg
2015-08-11 22:56 ` Nicolas Goaziou
2015-08-12 8:25 ` Meir Goldenberg [this message]
2015-08-12 13:03 ` Nicolas Goaziou
2015-08-18 15:32 ` Bastien
2015-08-23 15:26 ` Meir Goldenberg
2015-08-23 22:30 ` Nicolas Goaziou
2015-08-24 7:34 ` Meir Goldenberg
2015-08-27 18:18 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP1Du3VeiqHMZ0mxNdgPsFzV6L+dDxzXS1eu8_kUVSC6+H8M9w@mail.gmail.com \
--to=mgoldenbe@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).