Re: [O] ox-latex: default packages cleaning

[Rasmus]

Suvayu Ali <address@hidden> writes:

> The polyglossia bits work well.

> The file local variable prompt for every export is quite annoying
> though.  Same goes for the exported file, opening it brings up the same
> prompt again.  I guess it is a one time thing to mark that variable as
> safe, then it should be good.

It's probably too annoying to default org-latex-variant-file-string to a
file variable.  I find it neat to automatically have AUCTeX pick the right
engine, though.

I worry more about how to allow flags to be transmitted without making it
insecure.  E.g. -shell-escape is one that we'd want to allow for minted.
Perhaps whitelisted flags....  Or just allow arbitrary flags after a latex
command.

> I have a few other questions:
> - how does one change the variant when doing a subtree export?  By
>   setting EXPORT_LATEX_VARIANT?

It seems to work at least to the point that the right engine is written to
the file:

#+LATEX_VARIANT: xelatex
* pdflatex
:PROPERTIES:
:export_latex_variant: pdflatex
:END:

* lualatex
:PROPERTIES:
:export_latex_variant: lualatex
:END:


> - Is it possible to set a default variant?

org-latex-variant => "pdflatex"

> - How does one insert a line in the package list which is not
>   usepackage.  I guess the normal case is still valid:
>   "\\somedirective", but inserting a similar variant specific directive
>   isn't possible.

Not possible ATM.  You could use iftex on the latex level or we could
allow something like '("\\mymacro" ("pdflatex")) and enforce the second
argument to be a list to differentiate it from ("PKG OPTIONS" "PKG")....

> I'm starting to wonder, all these complications, is it really worth it?
> What do you think?

Most of my longer documents declare the compiler via bind of file
variables.  So I'd use it.  It would also allow me to get rid of some
filters.

Rasmus

-- 
Warning: Everything saved will be lost