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: Sat, 06 Jun 2015 09:28:12 +0200 [thread overview]
Message-ID: <87eglpjnxv.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <878ubx224x.fsf@posteo.de> (Titus von der Malsburg's message of "Fri, 05 Jun 2015 15:58:54 -0700")
Titus von der Malsburg <malsburg@posteo.de> writes:
> Thee can be handled by protectedtexttt. The obvious questions is of
> course: Wouldn’t it be more consistent to handle all instances of ~code~
> using protectedtexttt?
One option would be indeed to remove \verb altogether. Note that it is
also used in inline source blocks.
However, I assume \verb put less limitations than \texttt on its
contents, so I'd rather keep \verb around.
> And if you want to support the use of \verb at all, shouldn’t that be
> done via =verbatim= not ~code~?
I fail to see how it would solve the problem at hand. It would simply
move it elsewhere.
My question is how to handle \verb at the LaTeX level, not at the Org
one.
>>> These two did not produce the intended results (sub and super script
>>> don’t work) but the LaTeX is not malformed:
>>>
>>> test^~test~
>>> test_~test~
>
> This really seems to be an independent issue (because test^*test*
> doesn’t work either)
Actually, I just realized this is not valid syntax for sub/superscript
in Org anyway. It should be
test^{~test~}
Regards,
next prev parent reply other threads:[~2015-06-06 7:26 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
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 [this message]
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=87eglpjnxv.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).