From: "Ryan C. Thompson" <rct2c@virginia.edu>
To: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Bug Report: TAB on empty headline cycles through the wrong levels
Date: Fri, 27 Nov 2009 14:36:33 -0800 [thread overview]
Message-ID: <4B105471.5020002@virginia.edu> (raw)
I have discovered a possible bug with the new 6.33 feature of cycling
empty headline levels with TAB. IT seems that org will always assume
that the initial level of the headline is the "base" level. Pressing TAB
once will always go one level deeper than that, to the "child" level,
TAB a second time will go one level shallower than the base level, and
so on.
the problem is that I expect the "base" level to be based on the
previous headline's level, not on the initial level of the empty
headline itself. The problem would not usually show itself, because if
you press meta+RET at the end of a headline, you get a new empty one at
the same level as the previous headline. However, if you press meta+RET
at the *beginning* of a headline (before the stars), you get a new empty
headline at the same level as the *next* headline, which might not be
the same level as the previous headline.
Here's a simple test case:
* Head1
** Head2
Put the point at the very beginning of the second heading, and press
meta+RET, then TAB. You should get this:
* Head1
*** [point is here]
** Head2
The following is what I would *expect* to get:
* Head1
* [point is here]
** Head2
So basically, the base level for depth cycling should be determined from
the previous headline, not the new blank headline. At least, that's what
I expected, and I can't think of any reason you would want to put a
level-3 headline under a level-1 headline.
-Ryan
next reply other threads:[~2009-11-27 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 22:36 Ryan C. Thompson [this message]
2009-11-30 16:40 ` Bug Report: TAB on empty headline cycles through the wrong levels 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B105471.5020002@virginia.edu \
--to=rct2c@virginia.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.