emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Ryan C. Thompson" <rct2c@virginia.edu>
Cc: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Bug Report: TAB on empty headline cycles through the wrong levels
Date: Mon, 30 Nov 2009 17:40:36 +0100	[thread overview]
Message-ID: <2939B61F-D1C6-4149-A07E-69782522C07B@gmail.com> (raw)
In-Reply-To: <4B105471.5020002@virginia.edu>

Hi Ryan,

here I do not agree with your assessment.
Putting the cursor at the beginning of a headline and pressing M-RET  
is a specific exception of the normal workings of the command, and it  
create a sibling above the entry.

If you want to make use of the indentation cycling, I think you should  
go to the end of the subtree above by pressing LEFT, and then use M- 
RET annd then TAB to get your level right.

- Carsten

On Nov 27, 2009, at 11:36 PM, Ryan C. Thompson wrote:

> 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
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

      reply	other threads:[~2009-11-30 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-27 22:36 Bug Report: TAB on empty headline cycles through the wrong levels Ryan C. Thompson
2009-11-30 16:40 ` 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=2939B61F-D1C6-4149-A07E-69782522C07B@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rct2c@virginia.edu \
    /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).