From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Problem with moving outline branches Date: Thu, 3 Jan 2008 10:18:03 +0100 Message-ID: References: <000a01c84a3d$87109310$6680a8c0@CUBE> Mime-Version: 1.0 (Apple Message framework v915) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JAMDK-0006fm-98 for emacs-orgmode@gnu.org; Thu, 03 Jan 2008 04:18:10 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JAMDJ-0006eg-7K for emacs-orgmode@gnu.org; Thu, 03 Jan 2008 04:18:09 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JAMDI-0006eV-NU for emacs-orgmode@gnu.org; Thu, 03 Jan 2008 04:18:09 -0500 Received: from ug-out-1314.google.com ([66.249.92.171]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JAMDI-0003KH-EQ for emacs-orgmode@gnu.org; Thu, 03 Jan 2008 04:18:08 -0500 Received: by ug-out-1314.google.com with SMTP id a2so2995639ugf.48 for ; Thu, 03 Jan 2008 01:18:07 -0800 (PST) In-Reply-To: <000a01c84a3d$87109310$6680a8c0@CUBE> 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: Chris Randle Cc: emacs-orgmode@gnu.org On Dec 29, 2007, at 6:09 PM, Chris Randle wrote: > Hi All > > I believe that there have been some recent changes to the way that > trailing blank lines at the end of nodes are treated. Most (but not > all) > of my notes under nodes have a single trailing line before the next > node, for example: > > * Task 1 > ** Task 1a > ** Task 1b > Notes for 1b > > ** Task 1c > Notes for 1c > > ** Task 1d > * Task 2 > > If the tree is fully expanded, and I place the cursur on "** Task 1b" > and do M-down, the nodes 1b and 1c are re-ordered as expected. > > If the tree us exanded to only the 2nd level, as follows: > > * Task 1 > ** Task 1a > ** Task 1b... > ** Task 1c... > ** Task 1d > * Task 2 > > And I do a M-down on node 1b, "** Task 1b" is visually tacked on to > the > end of the line occupied by "** Task 1c". Yes, I can reproduce this bug. > > > In this instance it seems to be cosmetic, as closing and opening the > tree fixes the visual corruption, but I've had other instances (not > reproduced) where I've moved things up and down a few times in a more > complex tree, and the "corruption" is not just visual: nodes becomes > subsumed by others. Is this only recently, or have you had this problem before? - Carsten