emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alain.Cochard@unistra.fr
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "Alain.Cochard@unistra.fr" <Alain.Cochard@unistra.fr>,
	Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Mistake in LaTeX syntax not detected, strange pdf generated
Date: Tue, 29 Nov 2022 12:33:33 +0100	[thread overview]
Message-ID: <25477.60941.565115.403533@gargle.gargle.HOWL> (raw)
In-Reply-To: <87cz963t98.fsf@ucl.ac.uk>

Fraga, Eric writes on Tue 29 Nov 2022 11:16:

 > I think having the expectation that org will parse within LaTeX
 > blocks may be a little unrealistic.

Org, no, but (pdf)latex yes.

 > But, also, what should it do?

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.

-- 
EOST (École et Observatoire des Sciences de la Terre) 
ITE (Institut Terre & Environnement) | alain.cochard@unistra.fr
5 rue René Descartes   [bureau 110]  | Phone: +33 (0)3 68 85 50 44 
F-67084 Strasbourg Cedex, France     | [ slot available for rent ]



  reply	other threads:[~2022-11-29 11:34 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 [this message]
2022-11-29 11:51         ` Alain.Cochard
2022-11-29 12:20           ` Dominik Schrempf
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=25477.60941.565115.403533@gargle.gargle.HOWL \
    --to=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
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).