From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-preview-latex-process-alist's :latex-header should not fall back to org-format-latex-header [9.3.4 (9.3.4-5-ga0f3bb-elpaplus @ /home/lockywolf/.emacs.d/elpa/org-plus-contrib-20200210/)]
Date: Thu, 30 Apr 2020 17:28:45 +0200 [thread overview]
Message-ID: <87wo5x9emq.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87d07r9dhx.fsf@delllaptop.lockywolf.net> (Vladimir Nikishkin's message of "Wed, 29 Apr 2020 11:28:42 +0800")
Hello,
Vladimir Nikishkin <lockywolf@gmail.com> writes:
> There are two almost unrelated latex-using processes in org. One is
> export, the other one is generating previews.
>
> The latter one is far less demanding than the former. Previews only care
> about certain math, whereas exports may very well be super tricky.
>
> Therefore, preparing org documents for export often includes setting a
> separate latex compiler (in 99% of the cases lualatex or xelatex), and a
> custom #+LATEX_HEADER. the latex compiler controlled with
> (setq org-latex-compiler "lualatex")
> (setq org-latex-bib-compiler "biber")
> is completely ignored by the preview process. This is fine, since
> previews only care about small things. However, #+LATEX_HEADER is _not_
> ignored, which means that previews will fail to compile, since
> LATEX_HEADER is prepared for a different compiler.
IIRC, LATEX_HEADER_EXTRA is meant for non-preview compilation.
LATEX_HEADER is for both preview and export.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2020-04-30 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 3:28 Bug: org-preview-latex-process-alist's :latex-header should not fall back to org-format-latex-header [9.3.4 (9.3.4-5-ga0f3bb-elpaplus @ /home/lockywolf/.emacs.d/elpa/org-plus-contrib-20200210/)] Vladimir Nikishkin
2020-04-30 15:28 ` Nicolas Goaziou [this message]
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=87wo5x9emq.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=lockywolf@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).