From: Carsten Dominik <carsten.dominik@gmail.com>
To: Matthew Lundin <mdl@imapmail.org>
Cc: Bernt Hansen <bernt@norang.ca>,
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: Fri, 23 Oct 2009 00:11:48 +0200 [thread overview]
Message-ID: <AE167B54-6B04-441F-91E4-694440A0276B@gmail.com> (raw)
In-Reply-To: <m28wf3jdv5.fsf@fastmail.fm>
On Oct 22, 2009, at 11:52 PM, Matthew Lundin wrote:
> Carsten Dominik <carsten.dominik@gmail.com> writes:
>
>> On Oct 22, 2009, at 10:23 PM, Matt Lundin wrote:
>>
>>> Bernt Hansen <bernt@norang.ca> writes:
>>>
>>>> "Tim O'Callaghan" <tim.ocallaghan@gmail.com> 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
prev parent reply other threads:[~2009-10-22 22:11 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
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 [this message]
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=AE167B54-6B04-441F-91E4-694440A0276B@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).