From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files, Date: Thu, 22 Oct 2009 22:28:04 +0200 Message-ID: References: <3d6808890910221255j3ed36d34t63366fb6da3309d2@mail.gmail.com> <87tyxr5gwj.fsf@gollum.intra.norang.ca> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N14Gc-0002d4-3f for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 16:28:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N14GX-0002cc-Hy for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 16:28:13 -0400 Received: from [199.232.76.173] (port=41375 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N14GX-0002cZ-C7 for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 16:28:09 -0400 Received: from mail-ew0-f206.google.com ([209.85.219.206]:35998) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N14GW-00050A-W0 for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 16:28:09 -0400 Received: by ewy2 with SMTP id 2so9076855ewy.31 for ; Thu, 22 Oct 2009 13:28:08 -0700 (PDT) In-Reply-To: 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: Matt Lundin Cc: Bernt Hansen , Tim O'Callaghan , org-mode On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote: > 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. Nope, it works for any variables. It is special that is *also* works for export variables, which is complicated because the *output buffer* is current when export happens, so local variables would be out of scope. - Carsten > > 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 > > > _______________________________________________ > Emacs-orgmode mailing list > Remember: use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten