From: Alain.Cochard@unistra.fr
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "Alain.Cochard@unistra.fr" <Alain.Cochard@unistra.fr>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Confused about source code blocks evaluation when exporting
Date: Fri, 22 Jul 2022 06:27:02 +0200 [thread overview]
Message-ID: <25306.10006.67482.871919@gargle.gargle.HOWL> (raw)
In-Reply-To: <87k0883qfb.fsf@ucl.ac.uk>
Fraga, Eric writes on Wed 20 Jul 2022 12:43:
> Maybe try this for your local variables (at the end of the org file):
>
> # Local Variables:
> # org-latex-pdf-process: ("...")
> # End:
>
> as a test (adjusting as you see fit)? This works for me. No need to
> use BIND.
Indeed, it works for me as well. Thanks. But the advantage of not
using 'setq' comes at the detriment of keeping related things together
in the file. Plus one must revisit the file when changing the value of
that variable. So it seems there is no satisfactory solution...
--
EOST (École et Observatoire des Sciences de la Terre)
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44
F-67084 Strasbourg Cedex, France | [ slot available for rent ]
next prev parent reply other threads:[~2022-07-22 4:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 12:53 Confused about source code blocks evaluation when exporting Alain.Cochard
2022-07-12 14:08 ` Fraga, Eric
2022-07-14 5:47 ` Rudolf Adamkovič
2022-07-12 14:22 ` Greg Minshall
2022-07-12 21:13 ` Alain.Cochard
2022-07-13 10:57 ` Fraga, Eric
2022-07-13 21:06 ` Alain.Cochard
2022-07-14 7:06 ` Fraga, Eric
2022-07-14 8:09 ` Alain.Cochard
2022-07-14 8:35 ` Fraga, Eric
2022-07-20 12:12 ` Alain.Cochard
2022-07-20 12:43 ` Fraga, Eric
2022-07-22 4:27 ` Alain.Cochard [this message]
2022-07-22 17:09 ` Fraga, Eric
2022-07-22 22:21 ` Alain.Cochard
2022-07-14 6:06 ` Rudolf Adamkovič
2022-07-14 6:48 ` Alain.Cochard
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=25306.10006.67482.871919@gargle.gargle.HOWL \
--to=alain.cochard@unistra.fr \
--cc=e.fraga@ucl.ac.uk \
--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 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).