From: "Thomas S. Dye" <tsd@tsdye.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [PATCH] Distinguish = and ~ delimiters in LaTeX export
Date: Sun, 30 Jan 2011 08:44:12 -1000 [thread overview]
Message-ID: <84A78870-6D14-4DBA-A6F3-7709102124A9@tsdye.com> (raw)
In-Reply-To: <80zkqinuxa.fsf@missioncriticalit.com>
On Jan 30, 2011, at 7:49 AM, Sébastien Vauban wrote:
> Hi Thomas,
>
> "Thomas S. Dye" wrote:
>> 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.
>
> What's the real use of that variable? I mean, wouldn't it be more
> simple if
> Org's export behavior was just based on the contents of
> org-export-latex-emphasis-alist? Is there verbatim in it, we use
> verbatim. Is
> is texttt in it, we use texttt...
>
> In fact, in which cases do we want to override what's described in
> the alist?
>
> Best regards,
> Seb
>
> --
> Sébastien Vauban
Aloha Seb,
Do you mean the variable org-export-latex-use-verb? I haven't looked
into its history in the git repo. Currently it defaults to nil, so
\verb is not used and \texttt is used in its place.
Carsten has a patch on the list today that changes the default to t,
which means that what you see in the alist is pretty much what you
get. For reasons having to do with typesetting code snippets (that I
don't fully understand), Carsten protects special characters in
\texttt. This means that the alist doesn't contain a markup character
that yields straight \texttt, though it should be straightforward to
add one.
I hope this helps. In any event, it represents the limit of my
understanding of what goes on in org-latex.el, which I freely admit
falls far short of full comprehension.
All the best,
Tom
next prev parent reply other threads:[~2011-01-30 18:44 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
2011-02-01 10:30 ` Bastien
2011-01-30 17:49 ` Sébastien Vauban
2011-01-30 18:44 ` Thomas S. Dye [this message]
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=84A78870-6D14-4DBA-A6F3-7709102124A9@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).