From: Aaron Ecay <aaronecay@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>,
Ken Mankoff <mankoff@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: BEGIN_LATEX_HEADER [cont]
Date: Sat, 21 Jun 2014 01:43:39 -0400 [thread overview]
Message-ID: <87mwd624xg.fsf@gmail.com> (raw)
In-Reply-To: <87simzu6f4.fsf@nicolasgoaziou.fr>
Hi Nicolas,
2014ko ekainak 20an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Ken Mankoff <mankoff@gmail.com> writes:
>
>> On 2014-06-20 at 04:50, Nicolas Goaziou wrote:
>>> I suggest to use existing solutions instead: configure
>>> `org-latex-classes'.
>>
>> I'm all for using existing solutions, but cannot see how I might use
>> this to easily customize export differently for different documents when
>> large amounts of LaTeX preamble code is being used.
>
> It's quite simple. You add your large amount of LaTeX preamble code in
> a new class, e.g., "my-class", in `org-latex-classes'. Then, in all
> documents needing this preamble code, you just add:
>
> #+latex_class: my-class
>
> Rinse and repeat for each document type.
There are two issues with this solution.
The first is that editing non-trivial latex code embedded in an elisp
string quickly becomes tedious, whereas it’s much pleasanter in org
using org-edit-special, syntax highlighting of src blocks, etc.
The second is that it’s impossible to share without distributing elisp
code. From the twin standpoints of reproducible research and security,
I think org ought to maximize the degree to which export use cases are
sharable without resorting to executing elisp code. There’s a threshold
beyond which it’s impossible to keep these goals, of course. But it’s
worth considering how org-latex-classes and friends might adapt to
increase the territory that falls within rather than outside the
Turing-complete boundary.
Just my 2 cents,
--
Aaron Ecay
next prev parent reply other threads:[~2014-06-21 5:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 23:37 BEGIN_LATEX_HEADER [cont] Ken Mankoff
2014-06-19 23:48 ` Aaron Ecay
2014-06-20 7:51 ` Sebastien Vauban
2014-06-20 8:50 ` Nicolas Goaziou
2014-06-20 11:17 ` Ken Mankoff
2014-06-20 11:52 ` Fabrice Popineau
2014-06-20 12:11 ` Nicolas Goaziou
2014-06-21 5:43 ` Aaron Ecay [this message]
2014-06-21 8:16 ` Nicolas Goaziou
2014-06-22 0:42 ` Aaron Ecay
2014-06-22 2:00 ` [ANN] ox-extras (was: BEGIN_LATEX_HEADER [cont]) Aaron Ecay
2014-06-22 22:07 ` [ANN] ox-extras Rasmus
2014-06-22 22:08 ` Rasmus
2014-06-23 19:57 ` Nicolas Goaziou
2014-06-23 20:29 ` Thomas S. Dye
2014-06-22 2:19 ` BEGIN_LATEX_HEADER [cont] Ken Mankoff
2014-06-22 9:36 ` Nicolas Goaziou
2014-06-22 9:35 ` Nicolas Goaziou
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=87mwd624xg.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=mankoff@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).