Hi,
[ ... ]
>
>>> Here's another of my pet-griefs
>>> - a
>>> - b
>>>
>>> | → M-RET will give me an itme
>>> | → M-RET will give me a headline
>>>
>>> Why is the behavior a function of amount of whitespace/newlines to
>>> nearest element? This makes not sense to me and goes against what I
>>>
Nicolas Goaziou writes:
> Rasmus writes:
>
>> I don't have a grand vision, but, ideally, I'd want M-RET to "do the
>> right thing", which is my book is often create an element similar to
>> element at point, and is certainly not but my #+begin_src emacs-lisp
>> code on a headline. I agree the l
Rasmus writes:
> I don't have a grand vision, but, ideally, I'd want M-RET to "do the
> right thing", which is my book is often create an element similar to
> element at point, and is certainly not but my #+begin_src emacs-lisp
> code on a headline. I agree the logical action is to the eye of th
Hi,
Nicolas Goaziou writes:
> Rasmus writes:
>
>> From my point of view, we can make every function tied to M-RET beyond
>> `org-insert-headline' configurable and turned off by default. This may,
>> however, also add confusion ("why did M-RET work in X's Org but not in
>> mine...").
>
> In thi
Hello,
Sebastien Vauban
writes:
> In a similar vein to this thread, I've always wondered if the following
> is normal or not.
>
> Having such a file:
>
> ** TODO Research
>
> - Who are the competitors?
> - What are our product's advantages?
> - Target market
> - Elevator pitch|
>
> Check out w
Hello,
In a similar vein to this thread, I've always wondered if the following
is normal or not.
Having such a file:
--8<---cut here---start->8---
** TODO Research
- Who are the competitors?
- What are our product's advantages?
- Target market
- Elevator pitc
