Re: Problem with moving outline branches

[Carsten Dominik <carsten.dominik@gmail.com>]

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