[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Orgmode] Feature Request? #+CONFIG keyword - to abstract more configura
From: |
Tim O'Callaghan |
Subject: |
[Orgmode] Feature Request? #+CONFIG keyword - to abstract more configuration into org files, |
Date: |
Thu, 22 Oct 2009 21:55:47 +0200 |
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?
Tim.
- [Orgmode] Feature Request? #+CONFIG keyword - to abstract more configuration into org files,,
Tim O'Callaghan <=
- [Orgmode] Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files,, Bernt Hansen, 2009/10/22
- [Orgmode] Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files,, Matt Lundin, 2009/10/22
- Re: [Orgmode] Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files,, Carsten Dominik, 2009/10/22
- Re: [Orgmode] Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files,, Tim O'Callaghan, 2009/10/22
- [Orgmode] Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files,, Matthew Lundin, 2009/10/22
- [Orgmode] Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files,, Carsten Dominik, 2009/10/22