From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Scott Randby <srandby@gmail.com>
Cc: emacs-orgmode@gnu.org, "Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: Multiple underscores crash org latex export; other exporters survive
Date: Sun, 04 Dec 2016 11:13:02 +0100 [thread overview]
Message-ID: <87bmwsatox.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <50e77033-c13c-c0be-5d4a-ec5c107e93ae@gmail.com> (Scott Randby's message of "Sat, 3 Dec 2016 23:53:38 -0500")
Hello,
Scott Randby <srandby@gmail.com> writes:
> There is an interesting issue here. I sometimes want to use ~ in a code
> snippet, so I can't use ~code snippet~. Yet,
Indeed, this was discussed in this ML. We need some escape character in
Org. A general escape character is a bit ambitious, and not necessarily
useful, but we could introduce one specifically for verbatim and code
markers, much like in macros and verbatim blocks, e.g.
~some\~code\=with special\\ characters~
There is a design decision involved: what character can be escaped? It
could be anything, or limit to "~" for code and "=" for verbatim
markers. For example macros limit escape-able characters to "," and "\".
This makes the contents easier to read, but the rule is inconsistent.
Thoughts?
> Org code: \verb@a_variable_deleteThisAndItWorks@
>
> Exported LaTeX: \verb@a\(_{\text{variable}}_{\text{deleteThisAndItWorks}}\)@
>
> The exported LaTeX is not what we want. Instead,
>
> Org code: #+latex:\verb@a_variable_deleteThisAndItWorks@
>
> Alternative: @@latex:\verb@a_variable_deleteThisAndItWorks@@@
>
> Exported LaTeX: \verb@a_variable_deleteThisAndItWorks@
>
> I've wondered why \verb isn't exported correctly without specifying it
> as literal LaTeX,
It's because Org recognize LaTeX commands only if they are followed by
a blank character, the end of buffer, or "{}", which is not the case
with \verb@...@.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-12-04 10:13 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 [this message]
2016-12-04 16:03 ` Scott Randby
2016-12-05 8:36 ` Scott Otterson
2016-12-06 1:33 ` Scott Randby
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmwsatox.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=srandby@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.