[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] BEGIN_LATEX_HEADER [cont]
From: |
Aaron Ecay |
Subject: |
Re: [O] BEGIN_LATEX_HEADER [cont] |
Date: |
Sat, 21 Jun 2014 01:43:39 -0400 |
User-agent: |
Notmuch/0.17+171~gbc10f63 (http://notmuchmail.org) Emacs/24.3.50.2 (x86_64-unknown-linux-gnu) |
Hi Nicolas,
2014ko ekainak 20an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Ken Mankoff <address@hidden> 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
- [O] BEGIN_LATEX_HEADER [cont], Ken Mankoff, 2014/06/19
- Re: [O] BEGIN_LATEX_HEADER [cont], Aaron Ecay, 2014/06/19
- Re: [O] BEGIN_LATEX_HEADER [cont], Sebastien Vauban, 2014/06/20
- Re: [O] BEGIN_LATEX_HEADER [cont], Nicolas Goaziou, 2014/06/20
- Re: [O] BEGIN_LATEX_HEADER [cont], Ken Mankoff, 2014/06/20
- Re: [O] BEGIN_LATEX_HEADER [cont], Fabrice Popineau, 2014/06/20
- Re: [O] BEGIN_LATEX_HEADER [cont], Nicolas Goaziou, 2014/06/20
- Re: [O] BEGIN_LATEX_HEADER [cont],
Aaron Ecay <=
- Re: [O] BEGIN_LATEX_HEADER [cont], Nicolas Goaziou, 2014/06/21
- Re: [O] BEGIN_LATEX_HEADER [cont], Aaron Ecay, 2014/06/21
- [O] [ANN] ox-extras (was: BEGIN_LATEX_HEADER [cont]), Aaron Ecay, 2014/06/21
- Re: [O] [ANN] ox-extras, Rasmus, 2014/06/22
- Re: [O] [ANN] ox-extras, Rasmus, 2014/06/22
- Re: [O] [ANN] ox-extras, Nicolas Goaziou, 2014/06/23
- Re: [O] [ANN] ox-extras, Thomas S. Dye, 2014/06/23
- Re: [O] BEGIN_LATEX_HEADER [cont], Ken Mankoff, 2014/06/21
- Re: [O] BEGIN_LATEX_HEADER [cont], Nicolas Goaziou, 2014/06/22
- Re: [O] BEGIN_LATEX_HEADER [cont], Nicolas Goaziou, 2014/06/22