Ihor Radchenko <[email protected]> writes: > Sławomir Grochowski <[email protected]> writes: > >> The resulting buffer is currently: >> >> Intro >> #+COLUMNS: %TODO >> * H
I've never managed to trigger this behavior, but yes, it would be confusing if I did. >> A minimal behavior change would be to remove the call to >> `outline-next-heading' and insert the keyword at the beginning of the >> buffer instead: I'd prefer the next option, but this one does have the virtues of simplicity and consistency with how org-mobile-timestamp-buffer currently inserts LAST_MOBILE_CHANGE timestamps, which is the only other automatic buffer-setting insertion I'm aware of (are there others?). >> Another possible policy would be to insert it after an initial block of >> file-level keywords, i.e. after consecutive keyword lines near >> `point-min' before the first non-keyword, non-blank line: >> >> #+TITLE: Notes >> #+AUTHOR: Me >> #+COLUMNS: %TODO > > Sticking to that block (if it exists) will make sense, yes. +1. I'd prefer my own buffer settings on top and any automatically inserted one to come immediately below my own. But that's a matter of taste. >> This would keep COLUMNS with other file-level settings without moving it >> past ordinary introductory text. It is a bit more complex than simply >> inserting at `point-min', though, and I am not aware of an existing Org >> helper that implements exactly this insertion policy. Maybe we should have one, though. We could probably think of other uses beside org-columns and org-mobile. (Discoverable buffer settings inserted via a single magit-like menu?) Regards, Christian
