emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: ox-latex: default packages cleaning
Date: Thu, 16 Jul 2015 10:49:40 +0200	[thread overview]
Message-ID: <87y4igxza3.fsf@gmx.us> (raw)
In-Reply-To: 20150716082958.GP18343@chitra.no-ip.org

Suvayu Ali <fatkasuvayu+linux@gmail.com> 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

  reply	other threads:[~2015-07-16  8:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 14:53 ox-latex: default packages cleaning Rasmus
2015-07-07 15:48 ` Eric S Fraga
2015-07-07 19:35 ` Suvayu Ali
2015-07-07 20:05   ` Rasmus
2015-07-07 20:52     ` Suvayu Ali
2015-07-07 21:07       ` Rasmus
2015-07-08 12:53   ` Rasmus
2015-07-08 13:43     ` Suvayu Ali
2015-07-08 13:53       ` Rasmus
2015-07-08 14:09         ` Suvayu Ali
2015-07-08 14:26           ` Rasmus
2015-07-08 14:55             ` Suvayu Ali
2015-07-08 15:41     ` Suvayu Ali
2015-07-08 16:06       ` Rasmus
2015-07-08 18:35       ` Rasmus
2015-07-16  8:29         ` Suvayu Ali
2015-07-16  8:49           ` Rasmus [this message]
2015-07-27  8:22             ` Sebastien Vauban
2015-07-27  8:30               ` Rasmus
2015-07-27  9:22                 ` Sebastien Vauban
2015-07-27  9:31                   ` Rasmus
2015-07-29 16:21           ` Rasmus
2015-07-08 12:54   ` Rasmus
2015-07-08 13:44     ` Suvayu Ali
2015-07-14 22:31   ` Marcin Borkowski
2015-07-15  8:33     ` Rasmus
2015-07-10 11:25 ` Robert Klein
2015-07-11 10:48   ` Rasmus
2015-07-11 18:53     ` Robert Klein
2015-07-13 10:08 ` Rasmus
2015-07-14 22:16 ` Marcin Borkowski

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=87y4igxza3.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).