From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files, Date: Thu, 22 Oct 2009 16:23:51 -0400 Message-ID: References: <3d6808890910221255j3ed36d34t63366fb6da3309d2@mail.gmail.com> <87tyxr5gwj.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N14CX-00065K-UO for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 16:24:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N14CS-00062v-B5 for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 16:24:00 -0400 Received: from [199.232.76.173] (port=42079 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N14CS-00062m-86 for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 16:23:56 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:34126) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N14CR-0004Cj-VQ for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 16:23:56 -0400 In-Reply-To: <87tyxr5gwj.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Thu, 22 Oct 2009 16:10:20 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Bernt Hansen Cc: Tim O'Callaghan , org-mode Bernt Hansen writes: > "Tim O'Callaghan" writes: > >> Expand the #+ 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