From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Giacomo M <jackjackk@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Improving debugging experience of latex errors on export
Date: Wed, 7 Sep 2016 15:27:40 +0100 [thread overview]
Message-ID: <878tv3n5sz.fsf@ucl.ac.uk> (raw)
In-Reply-To: <39369403d1484a10a3704090b86e747b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Giacomo M.'s message of "Wed, 7 Sep 2016 14:18:05 +0000")
On Wednesday, 7 Sep 2016 at 14:18, Giacomo M wrote:
> I'm using latexmk w/ pdflatex for my org2pdf exports. When I get a "PDF
> file produced with errors.", then I go to "*Org PDF LaTeX Output*"
> buffer to try to understand what is happening.
[...]
> I was wondering whether this latex "debugging" setup could be also used
> during org export, and how, or more generally how I can improve the
> debugging experience of latex export errors.
I do pretty much the same as you: go to the LaTeX file to see if I can
identify the cause of the error reported in the PDF buffer. There's no
easy way to accomplish the same directly from org
unfortunately. Sometimes, the context given in the PDF output is enough
to point me to the right place in the org file but not often...
I look forward to seeing inputs from others on this.
I will say, however, that using org means less LaTeX errors than I would
usually encounter when writing LaTeX directly!
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.94.1, Org release_8.3.5-1070-g190476
next parent reply other threads:[~2016-09-08 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39369403d1484a10a3704090b86e747b@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-07 14:27 ` Eric S Fraga [this message]
2016-09-07 14:18 Improving debugging experience of latex errors on export Giacomo M
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=878tv3n5sz.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=jackjackk@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).