emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Dominik Schrempf <dominik.schrempf@gmail.com>
To: alain.cochard@unistra.fr
Cc: "Fraga, Eric" <e.fraga@ucl.ac.uk>, emacs-orgmode@gnu.org
Subject: Re: Mistake in LaTeX syntax not detected, strange pdf generated
Date: Tue, 29 Nov 2022 13:20:06 +0100	[thread overview]
Message-ID: <87r0xmvtk4.fsf@gmail.com> (raw)
In-Reply-To: <25477.62017.692555.855056@gargle.gargle.HOWL>

Hi!

I wanted to chime in here, because sometimes I do have a similar
problem.

Whenever I export to LaTeX + PDF, it is pretty difficult to see if the
compilation actually worked (or not). This is, because the compilation
happens asynchronously, and so, the message about the compilation
results in the modeling vanishes fast.

Usually, I open the LaTeX compilation buffer manually, but I think it
would be great if Org Mode was a bit more verbose about the result of
the compilation (not the actual export). Not sure how this would work
though... (Not very helpful, I know).

Thank you!
Dominik

Alain.Cochard@unistra.fr writes:

> Alain.Cochard@unistra.fr writes on Tue 29 Nov 2022 12:33:
>
>  > I would expect that the mistake be reported in the *Org PDF LaTeX
>  > Output* Compilation buffer.  So far, what I saw in that buffer was
>  > essentially what shows up when I run 'pdflatex org_generated_file.tex'
>  > from a terminal.  Not this time: the "regular" pdflatex compiles
>  > correctly, not the pdflatex that Org uses internally.
>
>  > I thought what Org did was simply run pdflatex+bibtex+etc. just as
>  > what one would do manually, but apparently there is some difference.
>
> Hum, I correct myself here: the compilation buffer does report the
> mistake (I hadn't looked at it).  Also, the manual compilation with
>
>    pdflatex org_generated_file.tex
>
> does generate the same pdf provided that I hit <return> many times.
> Also, I see that the message
>
>    PDF file produced with errors.
>
> appears in the *Messages* buffer.
>
> So perhaps Org could display this message in the minibuffer instead of
>
>    Running /usr/bin/xdg-open /home/cochard/Org/debug3.pdf...done
>
> which leads to the impression that the compilation is OK.

next prev parent reply	other threads:[~2022-11-29 12:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 10:28 Mistake in LaTeX syntax not detected, strange pdf generated Alain.Cochard
2022-11-29 10:40 ` Fraga, Eric
2022-11-29 11:11   ` Alain.Cochard
2022-11-29 11:16     ` Fraga, Eric
2022-11-29 11:33       ` Alain.Cochard
2022-11-29 11:51         ` Alain.Cochard
2022-11-29 12:20           ` Dominik Schrempf [this message]
2022-11-29 12:54             ` Immanuel Litzroth

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=87r0xmvtk4.fsf@gmail.com \
    --to=dominik.schrempf@gmail.com \
    --cc=alain.cochard@unistra.fr \
    --cc=e.fraga@ucl.ac.uk \
    --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

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