Re: Highlighting bug with org-agenda-set-restriction-lock

[Christian Moe <mail@christianmoe.com>]

Didn't `M-RET' on an ordinary line of text also turn that line into a
heading, about the same as doing `C-c *' on that line? At least with
point in the first column (not sure about other cases)? My memory may be
faulty, but lately I've found myself trying to do that, and scratching
my head that it's not working as I thought it did. (I agree, of course,
that the current behavior agrees with the docs, and that the behavior I
seem to remember was redundant, but I also seem to remember it as pretty
handy.)

Yours,
Christian


Bastien writes:

> Hi Bernt,
>
> Bernt Hansen <bernt@norang.ca> writes:
>
>> Org file has this
>>
>> ,----
>> | * One
>> | two
>> | three
>> | four
>> | five
>> `----
>>
>> Put the cursor on first column of line two and hit M-S-RET gives me this
>>
>> ,----
>> | * One
>> | two
>> | * TODO 
>> | three
>> | four
>> | five
>> `----
>
> Okay, I see this too.
>
>> It seems to work correctly when there is no heading above the text
>> (ie. One is not a headline)
>
> That's what I tested after your previous email, yes.
>
> I need to think harder about this and to get more feedback, because
> the new behavior seems the correct one to me.  Also, it is in sync
> with the docstring of `org-insert-heading-respect-content':
>
>   Non-nil means insert new headings after the current subtree.  When
>   nil, the new heading is created directly after the current line.
>                                            ^^^^^
>
> This is about *inserting* a new heading, not about turning the current
> line into a heading (which is fine to have when there is no heading
> above, of course.)  Also, reverting to the old behavior would move
> S-M-RET closer to C-c *.
>
> Let's see if other users find the current behavior annoying, and let
> me know how annoying it is to you!
>
> Thanks,