From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Feature Request? #+CONFIG keyword - to abstract more configuration into org files, Date: Fri, 23 Oct 2009 00:11:48 +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 1N15sz-0007wV-CJ for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 18:11:57 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N15su-0007vE-K0 for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 18:11:56 -0400 Received: from [199.232.76.173] (port=48540 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N15su-0007vB-FN for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 18:11:52 -0400 Received: from mail-ew0-f228.google.com ([209.85.219.228]:60618) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N15su-00030c-1r for emacs-orgmode@gnu.org; Thu, 22 Oct 2009 18:11:52 -0400 Received: by ewy28 with SMTP id 28so2330690ewy.42 for ; Thu, 22 Oct 2009 15:11:51 -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: Matthew Lundin Cc: Bernt Hansen , Tim O'Callaghan , org-mode On Oct 22, 2009, at 11:52 PM, Matthew Lundin wrote: > Carsten Dominik writes: > >> On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote: >> >>> Bernt Hansen writes: >>> >>>> "Tim O'Callaghan" writes: >>>> >>>> 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 >> > > Thanks for the explanation. I aplogize if I'm missing something, but I > can't seem to get the bind line to work. I've placed the following > line > at the top of an org file: > > ,---- > | #+BIND: org-footnote-section "References" > `---- > > ...and yet after killing, reloading, and refreshing the buffer, the > footnotes still appear in the section in which they are entered, in > keeping with my global org-footnote-section setting (nil). > > Out of curiosity, I've also tried the following line to no avail: > > ,---- > | #+BIND: org-footnote-section t > `---- > > I've tried setting org-export-allow-BIND and org-export-allow-BIND- > local > to t, but the same results occur. > > On the other hand, when I use local variables, as below, the footnotes > appear under the headline "References". > >>> ,---- >>> | * COMMENT Local Variables >>> | # Local Variables: >>> | # org-footnote-section: "References" >>> | # End: >>> `---- > > Do I have the correct syntax for #+bind? Is there another variable > that > activates "bind" syntax? Or does it perhaps work only for certain > variables? You are right, I was mistaken! In fact, BIND works for any variables, but only during export :-) - Carsten