emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alain.Cochard@unistra.fr
To: emacs-orgmode@gnu.org
Subject: Problems with LaTeX export for $x\text{foo $x$}$-like construts?
Date: Wed, 28 Dec 2022 14:57:12 +0100	[thread overview]
Message-ID: <25516.19256.621545.995694@gargle.gargle.HOWL> (raw)


Version used: release_9.6-149-g554935 

With an org file containing only

   #+begin_export latex
   $x \text{foo $y$}$

   \(x \text{foo \(y\)}\)

   $x \text{foo \(y\)}$

   \(x \text{foo $y$}\)
   #+end_export

the pdf generated upon latex export gives as expected, i.e., with 'x'
and 'y' in mathematical font.

Maybe this is fully normal, but I find it annoying: when the 4 lines
above are not within a latex block, only the last 2 (that is, with
mixed "$...$" and "\(...\)" constructs), are shown correctly on the
resulting pdf.

The 1st one shows, on the pdf

   $x foo y$
   
(with 'y' in mathematical font).

The 2nd one (if alone in the org file) gives

   File "/home/cochard/Org/debug.pdf" wasn’t produced.  See "*Org PDF
   LaTeX Output*" for details


PS/incidentally: if one adds a blank line and another line to that 2nd
one, i.e., if the org file contains something like

   \(x \text{foo \(y\)}\)

   foo

then a pdf is generated, which shows

   x
   foo

The *Messages* buffer contains

   PDF file produced with errors.
   Running /usr/bin/xdg-open /home/cochard/Org/debug.pdf...done

but only the last of those lines is seen in the minibuffer.  So this
adds another example to those discussed in thread
https://list.orgmode.org/25477.57044.35186.766042@gargle.gargle.HOWL/
where one (at least I) would like to more permanently see "PDF file
produced with errors."


-- 
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-12-28 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 13:57 Alain.Cochard [this message]
2022-12-29 10:04 ` Problems with LaTeX export for $x\text{foo $x$}$-like construts? Ihor Radchenko
2022-12-29 10:39   ` Alain.Cochard
2022-12-29 10:44     ` Ihor Radchenko
2022-12-29 11:52   ` Ihor Radchenko

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=25516.19256.621545.995694@gargle.gargle.HOWL \
    --to=alain.cochard@unistra.fr \
    --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).