From: Rainer M Krug <Rainer@krugs.de>
To: emacs-orgmode@gnu.org
Subject: Re: Specifying ATTR_LATEX document wide?
Date: Tue, 16 Jun 2015 12:28:03 +0200 [thread overview]
Message-ID: <m2twu80wy4.fsf@krugs.de> (raw)
In-Reply-To: <87eglcbv7g.fsf@selenimh.access.network> (Nicolas Goaziou's message of "Mon, 15 Jun 2015 21:57:55 +0200")
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Rainer M Krug <Rainer@krugs.de> writes:
>
>> Thanks for the clarification. Is there a technical or security reason
>> for this? because especially for export, file local variables would make
>> sense to avoid the #+BIND keywords?
>
> ISTR there is a technical reason for this. Under some circumstances,
> local variables are not activated during export. I cannot remember which
> ones, unfortunately.
>
Thanks for the info.
> Also, unlike to local variables, BIND keywords can be set through
> SETUPFILE keywords.
Oh the SETUPFILE - have never thought about that one.
Thanks,
Rainer
>
>
> Regards,
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 480 bytes --]
prev parent reply other threads:[~2015-06-16 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 10:17 Specifying ATTR_LATEX document wide? Rainer M Krug
2015-06-02 11:12 ` Suvayu Ali
2015-06-02 13:49 ` Nicolas Goaziou
2015-06-03 8:10 ` Rainer M Krug
2015-06-09 7:24 ` Nicolas Goaziou
2015-06-09 7:53 ` Rainer M Krug
2015-06-15 19:57 ` Nicolas Goaziou
2015-06-16 10:28 ` Rainer M Krug [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2twu80wy4.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.