From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Ryan C. Thompson" Subject: Bug Report: TAB on empty headline cycles through the wrong levels Date: Fri, 27 Nov 2009 14:36:33 -0800 Message-ID: <4B105471.5020002@virginia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NE9Qj-0001ah-36 for emacs-orgmode@gnu.org; Fri, 27 Nov 2009 17:36:45 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NE9Qc-0001UN-HG for emacs-orgmode@gnu.org; Fri, 27 Nov 2009 17:36:43 -0500 Received: from [199.232.76.173] (port=58938 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NE9Qc-0001UK-BV for emacs-orgmode@gnu.org; Fri, 27 Nov 2009 17:36:38 -0500 Received: from fork7.mail.virginia.edu ([128.143.2.177]:4731) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NE9Qc-0003HQ-0o for emacs-orgmode@gnu.org; Fri, 27 Nov 2009 17:36:38 -0500 Received: from localhost (localhost [127.0.0.1]) by fork7.mail.virginia.edu (Postfix) with ESMTP id 0A37A1F5163 for ; Fri, 27 Nov 2009 17:36:37 -0500 (EST) Received: from fork7.mail.virginia.edu ([127.0.0.1]) by localhost (fork7.mail.virginia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01057-08 for ; Fri, 27 Nov 2009 17:36:36 -0500 (EST) Received: from mail-pz0-f178.google.com (mail-pz0-f178.google.com [209.85.222.178]) by fork7.mail.virginia.edu (Postfix) with ESMTP id B30621F5151 for ; Fri, 27 Nov 2009 17:36:36 -0500 (EST) Received: by pzk8 with SMTP id 8so1291367pzk.8 for ; Fri, 27 Nov 2009 14:36:36 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: org-mode Mailinglist 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