From: Titus von der Malsburg <malsburg@posteo.de>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [Bug] ~Verbatim~ in headlines breaks LaTeX
Date: Sat, 30 May 2015 08:19:41 -0700 [thread overview]
Message-ID: <87twuu5bzv.fsf@posteo.de> (raw)
In-Reply-To: <87wpzqxz9m.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On 2015-05-30 Sat 01:09, Nicolas Goaziou wrote:
> Hello,
>
> Titus von der Malsburg <malsburg@posteo.de> writes:
>
>> Yes, I saw this thread after sending the previous email. According to
>> `org-latex-text-markup-alist', protectedtexttt should be used, which
>> seems like a good-enough solution for this problem. But for some reason
>> that doesn’t happen.
>
> It happens. However, verbatim is =...= whereas ~...~ is code. The former
> uses protectedtexttt while the latter uses \verb.
Huh, ~code~ is translated to \verb and =verbatim= is translated to
\texttt (plus escaping of some special characters)? If \verb is used at
all, shouldn’t it be generated by =verbatim= instead of by ~code~?
> Note that we could do better anyway and switch command depending on
> context.
Yes, I suppose anything is better than producing malformed LaTeX.
Titus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-05-30 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 3:38 [Bug] ~Verbatim~ in headlines breaks LaTeX Titus von der Malsburg
2015-05-30 4:32 ` Nick Dokos
2015-05-30 5:18 ` Titus von der Malsburg
2015-05-30 8:09 ` Nicolas Goaziou
2015-05-30 15:19 ` Titus von der Malsburg [this message]
2015-05-31 8:40 ` Nicolas Goaziou
2015-06-05 19:28 ` Titus von der Malsburg
2015-06-05 21:27 ` Nicolas Goaziou
2015-06-05 22:58 ` Titus von der Malsburg
2015-06-06 7:28 ` Nicolas Goaziou
2015-06-06 17:32 ` Titus von der Malsburg
2015-06-06 22:15 ` Suvayu Ali
2015-06-06 23:20 ` Nicolas Goaziou
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=87twuu5bzv.fsf@posteo.de \
--to=malsburg@posteo.de \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=ndokos@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 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).