From: "Thomas S. Dye" <tsd@tsdye.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Distinguish = and ~ delimiters in LaTeX export
Date: Sun, 30 Jan 2011 08:23:47 -1000 [thread overview]
Message-ID: <C17BE60A-4DB0-4659-BB90-A9094AC78ECE@tsdye.com> (raw)
In-Reply-To: <A6B771FB-7E8B-474E-8A12-E13363D78FFC@gmail.com>
On Jan 30, 2011, at 5:30 AM, Carsten Dominik wrote:
> Aloha Tom,
>
> On Jan 29, 2011, at 7:40 PM, Thomas S. Dye wrote:
>
>> Aloha all,
>>
>> The default value of org-export-latex-emphasis-alist treats the =
>> and ~ delimiters as \\verb. Both settings are ignored because org-
>> export-latex-use-verb is nil by default. The = and ~ delimiters
>> produce \texttt{} instead of \verb. This patch distinguishes = and
>> ~ by changing the default for = to \\texttt{%s}.
>>
>> The docstring has also been changed to refer to org-export-latex-
>> use-verb.
>>
>> With this patch, users exporting to LaTeX will be able to use = for
>> \texttt text in LaTeX moving environments and ~ for \verb text in
>> places where it is safe to use this construct.
>
> This is a pretty good patch, but I think we should still modify it.
> Org users traditionally use =stuff= to mark code pieces, and I think
> it is still important to escape special characters like ^ and ~ and
> others.
>
> The modified patch below does the following:
>
> - Like your patch, it makes Org use \\verb for the ~...~ emphasis.
> - For =...= emphasis, it uses a new keyword \\protectedtexttt.
> This will protect special characters and then do texttt. And I
> have extended the protection to include multiple hyphens by
> converting
> "--" to "-{}-".
>
> Do you agree with this solution?
>
> - Carsten
>
Aloha Carsten,
Yes, I do. Your patch works here for the use cases I had in mind.
I'm pleased that you were able to make the patch work for other use
cases as well. Also, I like having org-export-latex-use-verb default
to t instead of nil. It is nice to have the \verb command immediately
at hand.
Thanks for looking into this.
All the best,
Tom
next prev parent reply other threads:[~2011-01-30 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-29 18:40 [PATCH] Distinguish = and ~ delimiters in LaTeX export Thomas S. Dye
2011-01-30 15:30 ` Carsten Dominik
2011-01-30 15:32 ` Carsten Dominik
2011-01-30 18:23 ` Thomas S. Dye [this message]
2011-02-01 10:30 ` Bastien
2011-01-30 17:49 ` Sébastien Vauban
2011-01-30 18:44 ` Thomas S. Dye
2011-02-01 11:09 ` Bastien
2011-02-01 11:17 ` Carsten Dominik
2011-02-01 17:04 ` Bastien
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=C17BE60A-4DB0-4659-BB90-A9094AC78ECE@tsdye.com \
--to=tsd@tsdye.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.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).