From: Carsten Dominik <dominik@science.uva.nl>
To: Jason Dunsmore <jason.public@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: folding broken in sparse TODO tree
Date: Wed, 6 Jun 2007 08:45:06 +0200 [thread overview]
Message-ID: <42da4e4df78e9e9031a42a8c11064f85@science.uva.nl> (raw)
In-Reply-To: <f5e839ad0706011434k368d15acgbe76b680036d0c93@mail.gmail.com>
On Jun 1, 2007, at 23:34, Jason Dunsmore wrote:
> On 6/1/07, Carsten Dominik <dominik@science.uva.nl> wrote:
>>
>> On Jun 1, 2007, at 22:57, Jason Dunsmore wrote:
>>
>> > On 6/1/07, Carsten Dominik <dominik@science.uva.nl> wrote:
>> >>
>> >> On Jun 1, 2007, at 2:38, Jason Dunsmore wrote:
>> >>
>> >> > I think this may be a bug. When I show a sparse TODO tree with
>> >> > org-show-todo-tree, 4th level and deeper headings don't unfold
>> >> > correctly.
>> >>
>> >> This has nothing to do with level 4, but with the fact that you
>> >> have no final newline after the final line.
>> >>
>> >> Still, a bug, fixed for 4.76
>> >>
>> >
>> > 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?
This will be changed in the next version. TAB on such a line
will now make sure that the headline after the end of the
subtree (i.e. the next sibling or higher level entry)
is visible. I agree with you that this makes things more
consistent and self-explanatory. Thanks a lot!
- Carsten
prev parent reply other threads:[~2007-06-06 7:21 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
2007-06-06 6:45 ` Carsten Dominik [this message]
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=42da4e4df78e9e9031a42a8c11064f85@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=jason.public@gmail.com \
/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).