emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Matt Lundin <mdl@imapmail.org>
To: Bernt Hansen <bernt@norang.ca>
Cc: Tim O'Callaghan <tim.ocallaghan@gmail.com>,
	org-mode <emacs-orgmode@gnu.org>
Subject: Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files,
Date: Thu, 22 Oct 2009 16:23:51 -0400	[thread overview]
Message-ID: <m2d44fjhyg.fsf@fastmail.fm> (raw)
In-Reply-To: <87tyxr5gwj.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Thu, 22 Oct 2009 16:10:20 -0400")

Bernt Hansen <bernt@norang.ca> writes:

> "Tim O'Callaghan" <tim.ocallaghan@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

next prev parent reply	other threads:[~2009-10-22 20:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 19:55 Feature Request? #+CONFIG keyword - to abstract more configuration into org files, Tim O'Callaghan
2009-10-22 20:10 ` Bernt Hansen
2009-10-22 20:23   ` Matt Lundin [this message]
2009-10-22 20:28     ` Carsten Dominik
2009-10-22 21:35       ` Tim O'Callaghan
2009-10-22 21:52       ` Matthew Lundin
2009-10-22 22:11         ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2d44fjhyg.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=tim.ocallaghan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).