emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
To: flare <gabrielxaviersmith@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-preview-latex-fragment dvipng fix for packages in org-latex-packages-alist breaking 'latex' command
Date: Sun, 20 Sep 2020 08:04:31 +0200	[thread overview]
Message-ID: <b4df2fed-8ed9-6da1-0f09-fc194498ba8c@posteo.eu> (raw)
In-Reply-To: <87bli1gt25.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]


If I've understood your problem correctly, simply using ("" "fontspec" 
nil) in org-latex-packages-alist should fix your issue.

Per the documentation, this third argument stops the package from being 
used when compiling preview fragments.



Gabriel S. X. Smith writes:
> This is where my fix starts to come in. When org mode does the small
> export of the latex fragment it would include the contents of
> org-latex-packages-alist in the LaTex headers. Some packages (namely
> 'fontspec,' used for xelatex) would lead to a failure to create the
> dvi file when the .tex file was compiled with the necessary
> 'latex' command.
> To alleviate this problem I designed this wrapper function which
> sets org-latex-packages-alist to nil just before executing the
> org-latex-preview function.

[-- Attachment #2: Type: text/html, Size: 2390 bytes --]

  reply	other threads:[~2020-09-20  6:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-20  0:29 [PATCH] org-preview-latex-fragment dvipng fix for packages in org-latex-packages-alist breaking 'latex' command flare
2020-09-20  6:04 ` Sébastien Miquel [this message]
2020-12-14  6:17   ` Bastien

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:

  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=b4df2fed-8ed9-6da1-0f09-fc194498ba8c@posteo.eu \
    --to=sebastien.miquel@posteo.eu \
    --cc=emacs-orgmode@gnu.org \
    --cc=gabrielxaviersmith@gmail.com \


* 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


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).