Tim O'Callaghan tim.ocallag...@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.
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
On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
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
2009/10/22 Carsten Dominik carsten.domi...@gmail.com:
On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
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.
Carsten Dominik carsten.domi...@gmail.com writes:
On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
Bernt Hansen be...@norang.ca writes:
Tim O'Callaghan tim.ocallag...@gmail.com writes:
Can you use the #+BIND: keyword to set arbitrary variables and
achieve
the same result?
If I
On Oct 22, 2009, at 11:52 PM, Matthew Lundin wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
Bernt Hansen be...@norang.ca writes:
Tim O'Callaghan tim.ocallag...@gmail.com writes:
Can you use the #+BIND: keyword to set arbitrary
