emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Titus von der Malsburg <malsburg@posteo.de>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: [Bug] ~Verbatim~ in headlines breaks LaTeX
Date: Sun, 31 May 2015 10:40:04 +0200	[thread overview]
Message-ID: <87r3px5ee3.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87twuu5bzv.fsf@posteo.de> (Titus von der Malsburg's message of "Sat, 30 May 2015 08:19:41 -0700")

Titus von der Malsburg <malsburg@posteo.de> writes:

> Huh, ~code~ is translated to \verb and =verbatim= is translated to
> \texttt (plus escaping of some special characters)?

Correct.

> If \verb is used at all, shouldn’t it be generated by =verbatim=
> instead of by ~code~?

Why is that? Because \verb reminds =verbatim=? Really, both "code" and
"verbatim" syntax produces verbatim contents. Therefore both are
eligible for "\verb".

Anyway, you can customize `org-latex-text-markup-alist' to your liking.

>> Note that we could do better anyway and switch command depending on
>> context.
>
> Yes, I suppose anything is better than producing malformed LaTeX.

Could you give the list of all contexts requiring such a switch, and
what the result should be in each case?

Thank you.


Regards,

  reply	other threads:[~2015-05-31  8:50 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
2015-05-31  8:40         ` Nicolas Goaziou [this message]
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=87r3px5ee3.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=malsburg@posteo.de \
    --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).