Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files,

[Bernt Hansen <bernt@norang.ca>]

"Tim O'Callaghan" <tim.ocallaghan@gmail.com> writes:

> Simply,
>
> 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?

-Bernt