emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lawrence Bottorff <borgauf@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Org-mode: How to render latex inside ~code~
Date: Sat, 27 Feb 2016 21:32:48 +0000	[thread overview]
Message-ID: <CAFAhFSX_P+_f44AMvxN6GqrsBvGxJ04fQw0WrVDSueG0bkHpDw@mail.gmail.com> (raw)
In-Reply-To: <m2a8mlkhrx.fsf@tsdye.com>

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

Got it set

(custom-set-variables ... '(org-pretty-entities t) ...

but nothing changed. ~> (cons 1 nil) \to (1)~ still outputs the raw \to
even though in the buffer it changes.

On Sat, Feb 27, 2016 at 8:41 PM, Thomas S. Dye <tsd@tsdye.com> wrote:

> Aloha Lawrence,
>
> Lawrence Bottorff writes:
>
> > This seems a catch-22: I want to render code in an org-mode export (html
> or
> > latex pdf) where the snippet below done as a ~code block
> >
> >> (cons 1 nil) \to (1)
> >
> > actually renders \to as a proper right arrow (yields). Of course if I do
> the
> > snippet as inline latex
> >
> > $> (cons 1 nil) \to (1)$
> >
> > I get the properly rendered right arrow, but now it's not in the sans
> mono code
> > font. What can I do to have my cake and eat it too?
>
> \to is defined in org-entities.  Do you get what you want by setting
> org-pretty-entities non nil?
>
> All the best,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>

[-- Attachment #2: Type: text/html, Size: 1564 bytes --]

      reply	other threads:[~2016-02-27 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 20:24 Org-mode: How to render latex inside ~code~ Lawrence Bottorff
2016-02-27 20:41 ` Thomas S. Dye
2016-02-27 21:32   ` Lawrence Bottorff [this message]

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=CAFAhFSX_P+_f44AMvxN6GqrsBvGxJ04fQw0WrVDSueG0bkHpDw@mail.gmail.com \
    --to=borgauf@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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).