Bernt Hansen <be...@norang.ca> writes: > "Tim O'Callaghan" <tim.ocallag...@gmail.com> writes: > >> Expand the #+<KEYWORD> in-org file configuration possibilities with >> a #+CONFIG or similar keyword. >> >> The idea being to abstract more configuration into actual org files, >> and let extensions have an easy way to use #+KEYWORD configuration. I >> expect it could also be used to auto-load suitably registered >> extensions/contributions. >> >> So for example, my org-action-verb extension might use a line like: >> >> #+CONFIG org-action-verb TODO|NEXT Address Ask Buy Change Clarify >> >> Where there is handler function CONFIG:org-action-verb, that is >> defined as auto-loadable and called with the rest of the line to >> configure the extension. >> >> I guess this mechanism could also be extended to abstract more >> core-org configuration - such as agenda keys, stuck projects, or >> whatever. >> >> what do people think? > > Can you use the #+BIND: keyword to set arbitrary variables and achieve > the same result?
If I understand it correctly, #+BIND only works for export related variables. For local options that are not part of the default in-buffer syntax, I use Local Variables. E.g., ,---- | * COMMENT Local Variables | # Local Variables: | # org-footnote-section: "References" | # End: `---- Best, Matt _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
