From: Scott Randby <srandby@gmail.com>
To: Scott Otterson <scotto@sharpleaf.org>,
"Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Multiple underscores crash org latex export; other exporters survive
Date: Mon, 5 Dec 2016 20:33:57 -0500 [thread overview]
Message-ID: <e7dcc945-e1f2-4d57-719f-e9b3f1afd99e@gmail.com> (raw)
In-Reply-To: <CAPY3P0SEif_++YRan=0GAPoovmcQ7SEcv=ywBKH0LnCABcsXeQ@mail.gmail.com>
On 12/05/2016 03:36 AM, Scott Otterson wrote:
> Yes, there's a general question of how to escape multiple underscores.
>
> But there's a bigger question too: Should an org-doc that runs fine in
> other exporters cause a messy-to-debug crash when it's exported to
> Latex? Is that the Pandoc-like behavior that orgmode seems to be aiming
> for?
>
> I love org-mode. For years, I've used it as a project organizer,
> brainstorming tool, and extremely versatile notekeeper. I've already
> got a big investment in it, so I'll spend the time to track down this
> kind of problem.
>
> But I'd guess that such unexpected Latex crashes have driven new users
> back to Word or whatever.
I don't think you can blame Org for the crashes you've experienced. Org
exports the string "a_variable_deleteThisAndItWorks" to
"a\(_{\text{variable}}_{\text{deleteThisAndItWorks}}\)" which is not a
valid LaTeX expression. This invalid output is not the fault of Org, it
is the fault of the input string. Since there are different ways of
interpreting "a_variable_deleteThisAndItWorks," you have to tell Org
which interpretation you want it to make when you export to LaTeX. This
means additional markup of the string is required.
That the exported LaTeX file crashes your installation of pdfTeX (or
whatever TeX engine you use) when you process it is not the fault of
Org. The exported LaTeX file contains an invalid LaTeX expression that
came from a ambiguous string, so pdfTeX shows an error when processing
the LaTeX file. Using additional markup of the string so that Org
exports it as a valid LaTeX expression is the solution to the problem.
Scott Randby
next prev parent reply other threads:[~2016-12-06 1:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 19:40 Multiple underscores crash org latex export; other exporters survive Scott Otterson
2016-12-03 21:24 ` Scott Randby
2016-12-03 22:31 ` Charles C. Berry
2016-12-04 4:53 ` Scott Randby
2016-12-04 10:13 ` Nicolas Goaziou
2016-12-04 16:03 ` Scott Randby
2016-12-05 8:36 ` Scott Otterson
2016-12-06 1:33 ` Scott Randby [this message]
[not found] ` <CAPY3P0QcpouDjmNpmaY6FzNSNjZyHAGufrbVtSuBzPxr6mUAzg@mail.gmail.com>
2016-12-06 18:18 ` Scott Randby
2016-12-06 23:50 ` Nicolas Goaziou
2016-12-07 2:06 ` Scott Randby
2016-12-07 11:21 ` Nicolas Goaziou
2016-12-10 23:24 ` Scott Randby
2016-12-11 0:05 ` Nicolas Goaziou
2016-12-12 3:37 ` Scott Randby
2016-12-12 7:46 ` Nicolas Goaziou
2016-12-12 15:18 ` Scott Otterson
2016-12-13 12:54 ` Nicolas Goaziou
2016-12-05 17:30 ` Charles C. Berry
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=e7dcc945-e1f2-4d57-719f-e9b3f1afd99e@gmail.com \
--to=srandby@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=scotto@sharpleaf.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).