From: Scott Randby <email@example.com> To: firstname.lastname@example.org Subject: Re: LaTeX fragment preview weirdness Date: Thu, 3 Jun 2021 15:54:21 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> > On 6/2/21 1:28 PM, Nick Dokos wrote: >> You probably want #+LATEX_HEADER_EXTRA, not #+LATEX_HEADER. Do >> >> (info "(org) Latex header and sectioning") >> >> where it says: >> >> #+BEGIN_QUOTE >> The LaTeX export back-end appends values from ‘LATEX_HEADER’ and >> ‘LATEX_HEADER_EXTRA’ keywords to the LaTeX header. The docstring for >> ‘org-latex-classes’ explains in more detail. Also note that LaTeX >> export back-end does not append ‘LATEX_HEADER_EXTRA’ to the header when >> previewing LaTeX snippets (see *note Previewing LaTeX fragments::). >> #+END_QUOTE >> > On 6/2/21 2:19 PM, Scott Randby wrote: > > That worked after I deleted the old images in the ltximg directory. I hardly ever preview LaTeX fragments, but I'm changing #+latex_header: to #+latex_header_extra: everywhere. > I had to do a little extra work to get subtree export to work properly. Subtree export appears to also not append ‘LATEX_HEADER_EXTRA’ to the header. I had to add the values I need to the properties of the subtree using 'EXPORT_LATEX_HEADER_EXTRA'. This actually cleaned up a lot of the code, but it was work I'd been putting off. Scott
prev parent reply other threads:[~2021-06-03 19:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-02 16:53 Scott Randby 2021-06-02 17:28 ` Nick Dokos 2021-06-02 18:19 ` Scott Randby 2021-06-03 19:54 ` Scott Randby [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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: LaTeX fragment preview weirdness' \ /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
Code repositories for project(s) associated with this 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).