Hi Sebastien, On 7.9.2013, at 21:28, Sebastien Vauban <sva-n...@mygooglest.com> wrote:
> Hi Carsten, > > Carsten Dominik wrote: >> On 7.9.2013, at 14:11, "Sebastien Vauban" <sva-n...@mygooglest.com> wrote: >> >>> Since a little while, I've observed that point's position is not anymore >>> preserved when cycling buffer's view with S-TAB. >>> >>> Sometimes, point stays where it was (even when in the body of entries); >>> sometimes, not. >>> >>> See http://screencast.com/t/1sr6Lezk: >>> >>> - when on the first letter of "From", in that example, point's location is >>> preserved; >>> >>> - when on the second letter of it, point's location is lost: new position is >>> at the end of the level 1 parent... >>> >>> That's very annoying when you want to just look at your tree structure, but >>> don't expect to land somewhere else by doing so. >> >> you say "since a little while". Have you tried to bisect? > > Not yet. I have many Chinese plates turning at the moment, but I'll try to do > that very soon. And I have other problems to report or bisect: > > - not possible anymore to "cut" a code snippet in two parts with C-c C-v C-d > (demarcate block); already reported (without bisect), no answer; > > - not possible anymore to use C-a or C-e in code blocks to select regions; not > reported yet, though I reported similar problems with C-arrows (apparently > due to a change which is now officially part of 8.1). IMO, that renders > editing of code block in the original buffer much more annoying. I have asked Eric about this. > >> Or has it been like this always? > > In my mind, this did work before; or, at least, in (many) more cases than it > now does. > >> Also, I am not convinced that staying in invisible places is the >> right behavior at all. Even though I would agree that three S-TAB >> in a row should be a null operation. > > At the very least, we could agree that point should always be part of the > entry we were on; so never go up to the *parent* entry. I have fixed this now, point does now completely stay put during global cycling. > >> May be it would be better to use something like >> >> (org-display-outline-path nil t) >> >> to see where you are? > > I know where I am: I'm using that. But, sometimes (in fact, often), I want to > see the rest of the entries (brothers, parents, etc.) in the outline view. > > I simply expect to land back at the entry I was at, when having cycled > 3 times. > > Best regards, > Seb > > -- > Sebastien Vauban
signature.asc
Description: Message signed with OpenPGP using GPGMail
