From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Tim O'Callaghan" <tim.ocallaghan@gmail.com>
Subject: Feature Request? #+CONFIG keyword - to abstract more configuration
 into org files,
Date: Thu, 22 Oct 2009 21:55:47 +0200
Message-ID: <3d6808890910221255j3ed36d34t63366fb6da3309d2@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N13lf-0004zf-5u
	for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 15:56:15 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N13la-0004pL-Rx
	for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 15:56:14 -0400
Received: from [199.232.76.173] (port=33276 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N13la-0004oy-0q
	for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 15:56:10 -0400
Received: from mail-fx0-f228.google.com ([209.85.220.228]:44786)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <tim.ocallaghan@gmail.com>) id 1N13lZ-0008Nh-IE
	for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 15:56:09 -0400
Received: by fxm28 with SMTP id 28so9724481fxm.42
	for <emacs-orgmode@gnu.org>; Thu, 22 Oct 2009 12:56:07 -0700 (PDT)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: org-mode <emacs-orgmode@gnu.org>

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.