Bastien <[email protected]> writes:
> Kévin Le Gouguec <[email protected]> writes:
>
>> Great! One last snag that I can see: when inserting properties or
>> clocking in, the :LOGBOOK:, :PROPERTIES: and :END: lines are indented,
>> but the /first/ :property: or CLOCK: line remains at column 0.
>
> Er. Can you try this (hopefully last) patch and report any problem?
>
> Thanks for your patience in testing this!
Well, try as I might, I couldn't get this one to misindent 😃 And a good
thing too, I was about to run out of synonyms for wrinkles/nits/snags
and the like 😉
If anyone is wondering what these exchanges are all about: with
Bastien's latest patch[1], setting org-adapt-indentation to
'headline-data results in the following behaviour, *whether
electric-indent-mode is enabled or not*:
- "* heading RET" starts an unindented line (point goes to column 0).
- The drawers inserted by org-set-property and org-clock-in are
indented.
So, to bring the discussion back to the poll:
- If nil or 'headline-data becomes the default value, RET will no longer
indent regular text after a headline (even with electric-indent-mode).
- The difference will be whether :DRAWERS: are indented or not.
As far as I am concerned, my preference has become:
(1) 'headline-data (indented drawers)
(2) nil (nothing indented)
(3) t (the status quo)
although I suppose an argument could be made that 'headline-data might
be a bit "young" and as such, should not be used as default value…
Let's see what the poll yields 🙂
[1] Uncommited, to apply on branch maint:
https://orgmode.org/list/[email protected]/2-fix-indent.patch
