emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: folding broken in sparse TODO tree
Date: Mon, 4 Jun 2007 10:09:15 +0200	[thread overview]
Message-ID: <da5ef78f8b8f98ae2419d44bfba54301@science.uva.nl> (raw)
In-Reply-To: <f5e839ad0706011434k368d15acgbe76b680036d0c93@mail.gmail.com>


On Jun 1, 2007, at 23:34, Jason Dunsmore wrote:

>> > I think there is still a related bug in 4.76.  If you put the
>> > following in an empty buffer:
>> >
>> > * level 1
>> > ** TODO level 2.0
>> > ** level 2.1
>> > ** level 2.3
>> >
>> > Press C-c C-v, go to the level 2.1 header, and press Tab, it isn't
>> > unfolded and the EMPTY ENTRY message appears.
>>
>>
>> Well, the 2.1 is empty, or am I missing something???
>>
>
> Yes, well, there are no notes for that heading, but there are further
> level 2 items, which I expected to be unfolded by pressing Tab.  Would
> there be anything inconsistant with that behavior?  Otherwise, it's
> difficult for me to tell which items with "..." in a sparse TODO tree
> can be unfolded and which can't.  Maybe a different symbol can signify
> which items can't be unfolded if there is a problem with making Tab
> unfold further items at the same level.

Now I see what you mean.  No.
TAB only show what is below this entry, not what it coming after it.
The reason for this is that normally, you would start from Overview
mode and then work your way down using TAB.  In this case, when you
press TAB on "level 1", all level 2 entries will be shown,
so the situation you describe would never arise.

Now, when you use C-c C-v or any other sparse-tree command,
the tree is not displayed in a consistent state, in order
to allow for a compact display of the matches[1].

To get the tree locally back to a more consistent state, you can use
the command C-u C-c C-r.

However, I do see that it might be intuitive in the situation you
describe to allow TAB to make the tree more consistent as well.
Need to think a bit about this possibility.  Thanks for
the feedback.

- Carsten



[1] You could, in fact, make it even more compact by configuring
     org-show-following-heading to nil.


>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>

--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477

  reply	other threads:[~2007-06-04  8:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01  0:38 folding broken in sparse TODO tree Jason Dunsmore
2007-06-01  7:07 ` Carsten Dominik
2007-06-01 20:57   ` Jason Dunsmore
2007-06-01 21:18     ` Carsten Dominik
2007-06-01 21:34       ` Jason Dunsmore
2007-06-04  8:09         ` Carsten Dominik [this message]
2007-06-06  6:45         ` Carsten Dominik

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=da5ef78f8b8f98ae2419d44bfba54301@science.uva.nl \
    --to=dominik@science.uva.nl \
    --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).