On Sat, Dec 9, 2017 at 4:41 PM, Nathan Aclander
<nathan.aclan...@gmail.com> wrote:
>
> Nicolas Goaziou <m...@nicolasgoaziou.fr> writes:
>
>> I don't qualify this as a bug. These commands explicitly work when point
>> is at the beginning of an item. Indeed, the sub-item may be arbitrarily
>> large, contain tables... it would be confusing to move the whole
>> sub-list when its structure is out of sight.
>
> Why do you think it would be confusing to move the whole sub-list? Why
> would it be move confusing when the point is on the sub-item vs. when
> the point is on the parent item?
>
> I think the inconsistency is unintuitive here, and causes confusion. And
> I think since large sub-items already get moved when the point is
> at the beginning, it would make sense to also move them when the point
> is on the sub item.
>
> Nathan
I think what Nicolas is saying is this (^ is point):
* ^Heading
M-S-left/right works here.
* Heading
^content text
M-S-left/right does not work here. Let’s assume that it does work
here to be consistent with the feature/bug you are requesting.
* Heading
- foo
- bar
^second bar line
M-S-left/right does not work here. Let’s assume that it does work
here per the feature/bug you are requesting. Does it move bar, foo,
or Heading? What if the text is very long and you cannot see where
you are?
...
some very long text
^some very long text
some very long text
...
What M-S-left/right does would be very confusing.
