Re: [O] Outline cycling does not preserve point's position

[Sebastien Vauban]

Hi Carsten,

Carsten Dominik wrote:
> On 9.9.2013, at 10:23, Sebastien Vauban <address@hidden> wrote:
>> Carsten Dominik wrote:
>>> On 9.9.2013, at 10:11, "Sebastien Vauban" <address@hidden> wrote:
>>>> Carsten Dominik wrote:
>>>>>> - 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.
>>>> 
>>>> Regarding C-down, is it possible to get it back working for selecting
>>>> parts of code?
>>>> 
>>>> In the video captured at http://screencast.com/t/1WjWohviyjE, we see that
>>>> we can move from an heading to the next with C-down (which is a nice
>>>> extra addition to the already existing speed commands), but also select
>>>> subelements in a region (paragraphs or list items).
>>>> 
>>>> Though, in the code block, C-down still looses the region...
>>> 
>>> is this about loosing the active mark, or about the effect that C-down now
>>> jumps elements, not paragraphs?
>> 
>> In fact, both... If we wanna still allow nice editing of code blocks,
>> without forcing the users to use the indirect buffer, one must be able to
>> quickly select, let's say a defvar, and copy it somewhere else; like we
>> would do in the programming mode buffer (and like we did in the Org buffer,
>> up to the change with C-down).
>
> So maybe you just want to bing C-down to forward-paragraph again?

This is a possibility, yes, but it completely defeats the nice `C-down' add-on
(when outside of code block), and I guess I won't be the only one with that
"problem".

Of course, the nicest would be to have both: the current `C-down' for text,
and the "programmatic" behavior when _in code blocks_. Maybe, that's not
possible, though...

Best regards,
  Seb

-- 
Sebastien Vauban