From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: About exporting
Date: Thu, 01 Apr 2021 18:00:10 +1100 [thread overview]
Message-ID: <871rbuiiog.fsf@gmail.com> (raw)
In-Reply-To: <8735wacx8b.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
>> And there is a final thing which (for me) seem to work better in
>> latex-mode compared to org. That's jumping to the ``next error'' with
>> some key stroke. That's important, LaTeX's own error output it quite
>> poor, but jumping to error locations is vital.
>
> Yes, this is an issue I have as well. And the fact that the error
> messages are for the LaTeX lines, not the org lines, so you end up
> sometimes having to look at the LaTeX code and then go back to the org
> file. This definitely adds friction!
>
>> I would not be surprised if some of that is somehow supported by org as
>> well (for TeX), only I have not figured it out, or perhaps I was too
>> lazy to figure it out how.
>
> No, I don't think there's anything (at the moment) to help with this. I
> would love to be proven wrong, mind you! Org always has more
> capabilities than I know...
the only small bit of help I've found is org-lint, which has helped me
find issues in the past. Doesn't help track down errors from *.tex ->
pdf etc, but often an error in the org file causes the errors in the
*.tex export.
Having said that, I find the most common cause of errors in the *.tex
export is due to in-line Latex in my org file. I rarely run into errors
due to export of 'normal' org content.
When I do run into problems, I just open the *.tex file in Auctex mode
and track it down that way. Usually, it isn't too hard to work out where
that relates back to the source org file. Being able to do that
semi-automatically would be nice, but I think something that would be
very difficult to implement. You would need something to parse the tex
error output, extract text which could be then searched for in the org
file. As mentioned, the problem is tex errors don't always contain that
information, so you would probably also have to parse the tex file and
then try to map that back to the corresponding part of the org file
(which assumes of course that it is the org data which has caused the
issue and not something relating to latex package or package
configuration).
--
Tim Cross
next prev parent reply other threads:[~2021-04-01 7:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.51.1617033608.26133.emacs-orgmode@gnu.org>
2021-03-29 19:37 ` About exporting Ypo
2021-03-29 20:15 ` William Denton
2021-03-29 20:46 ` autofrettage
2021-03-29 21:39 ` Samuel Wales
2021-03-29 21:31 ` Juan Manuel Macías
2021-03-29 22:06 ` Tim Cross
2021-03-30 6:17 ` Eric S Fraga
2021-03-30 8:01 ` Colin Baxter
2021-03-30 8:13 ` Detlef Steuer
2021-03-30 10:15 ` Eric S Fraga
2021-03-30 11:40 ` Joost Kremers
2021-03-30 8:17 ` Eric S Fraga
2021-03-30 11:04 ` Juan Manuel Macías
2021-03-29 22:26 ` Thomas S. Dye
2021-03-30 4:47 ` Greg Minshall
2021-03-30 11:54 ` Martin Steffen
2021-03-30 12:44 ` autofrettage
2021-03-30 14:35 ` Martin Steffen
2021-03-30 14:44 ` autofrettage
2021-03-30 15:44 ` Juan Manuel Macías
2021-03-31 9:59 ` Eric S Fraga
2021-03-31 18:28 ` Martin Steffen
2021-04-01 6:52 ` Eric S Fraga
2021-04-01 7:00 ` Tim Cross [this message]
2021-04-01 7:29 ` Eric S Fraga
2021-04-01 8:50 ` Timothy
2021-04-01 11:33 ` Eric S Fraga
2021-04-01 13:25 ` Timothy
2021-04-02 14:06 ` Eric S Fraga
2021-04-01 14:21 ` Juan Manuel Macías
2021-03-30 20:49 ` Tim Cross
2021-03-31 18:56 Juan Manuel Macías
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=871rbuiiog.fsf@gmail.com \
--to=theophilusx@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).