From: Zhuohua Li <lizhuohua1994@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug: `org-babel-latex-preamble' should not hardcode `pgfsysdriver' [9.4.4 (release_9.4.4 @ /home/n/.emacs.d/elpa/28.0/develop/org-mode/lisp/)]
Date: Mon, 6 Sep 2021 15:02:58 +0800 [thread overview]
Message-ID: <CALdQSHsFYAZNaOb9TRrHV78=UvzfBeJcRWeJUi3AGzpkFWPXhg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
------------------------------------------------------------------------
Hi, I tried to export LaTex code blocks into SVG images using the
development version org-mode (d70f280678) but failed with "PDF produced
with errors".
I found that in file `lisp/ob-latex.el', variable
`org-babel-latex-preamble' hardcodes the following:
\\def\\pgfsysdriver{pgfsys-tex4ht.def}
This only compiles if you use `htlatex', however, the default LaTex
compiler is `pdflatex`.
I deleted this line and everything works fine. I think this should be a bug
so I report it here. Hope it can be fixed.
Thank you very much!
Zhuohua
Emacs : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.29, cairo version 1.16.0)
of 2021-08-28
Package: Org mode version 9.4.4 (release_9.4.4 @
/home/n/.emacs.d/elpa/28.0/develop/org-mode/lisp/)
[-- Attachment #2: Type: text/html, Size: 2340 bytes --]
next reply other threads:[~2021-09-06 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 7:02 Zhuohua Li [this message]
2021-12-30 9:24 ` Bug: `org-babel-latex-preamble' should not hardcode `pgfsysdriver' [9.4.4 (release_9.4.4 @ /home/n/.emacs.d/elpa/28.0/develop/org-mode/lisp/)] Timothy
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='CALdQSHsFYAZNaOb9TRrHV78=UvzfBeJcRWeJUi3AGzpkFWPXhg@mail.gmail.com' \
--to=lizhuohua1994@gmail.com \
--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).