Hello,
Achim Gratz writes:
> I actually like the ability to split lines with M-RET, especially since
> there doesn't seem to be a sane way to tell org that "yes I want to
> split the line this time". What I want is that "point at EOL" is
> recognized as a special situation, much like "point at
Bernt Hansen writes:
> I use C-RET for inserting new headings and respecting content.
That _only_ works for headings, not items. C-RET always inserts a new
heading (and BTW, it does treat BOL specially, too).
> M-RET should NOT respect content in my setup so I think your
> suggestion would make
Achim Gratz writes:
> Nicolas Goaziou writes:
>> By default, M-RET is allowed to split lines, and therefore contents.
>
> Let me re-formulate my request:
>
> If the point is at EOL, there actually is no line to split and it
> would be far
> more logical if the new heading/item would simply be in
Nicolas Goaziou writes:
> By default, M-RET is allowed to split lines, and therefore contents.
Let me re-formulate my request:
If the point is at EOL, there actually is no line to split and it would be far
more logical if the new heading/item would simply be inserted after the
current one (inclu
Hello,
Achim Gratz writes:
> The command M-RET actually does what it's docstring says (insert before
> when point is at BOL, split line when it is inside), but there is
> inconsistent behaviour when point is at EOL, IMHO. Consider the
> following list (or equivalent headline structure), with poi
The command M-RET actually does what it's docstring says (insert before
when point is at BOL, split line when it is inside), but there is
inconsistent behaviour when point is at EOL, IMHO. Consider the
following list (or equivalent headline structure), with point after
"":
-
+ abbb
+
