Re: [O] Highlighting bug with org-agenda-set-restriction-lock

[Bernt Hansen]

Bastien <address@hidden> writes:

> 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!

OK.  If this is working as designed I'm fine with that.  I'll just
change my habits :)  I actually didn't read the docstring was just
basing it on previous behaviour (which may have been incorrect).

Thanks,
Bernt