emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: org-preview-latex-fragment is very picky
Date: Mon, 06 May 2013 09:52:43 +0200	[thread overview]
Message-ID: <87fvy05yus.fsf@mat.ucm.es> (raw)
In-Reply-To: 87mws9z1n8.fsf@pank.eu

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

>> "rasmus" == rasmus  <Rasmus> writes:

   > Uwe Brauer <oub@mat.ucm.es> writes:
   > Probably not.

   > Note these are Org features irrespective of fragment preview.  There
   > was some talk about it not so long ago.

   > Basically, it just happens that $·$ works as desired most of the time.
   > The proper way in LaTeX as well as in Org is \(·\).  Often you'll find
   > that in challenging cases you're better off with \(·\).

   > To see whether $·$ will work I use

   >   (setq org-highlight-latex-and-related '(latex))

   > To have nice symbols making preview of fragments less dire I use
   > pretty entities:

   >   (setq org-pretty-entities t)

   > Pretty entities can also be turned on locally.  For missing glyphs
   > you're using you can do something like:

   >   (setq org-entities-user '(("implies" "\\Rightarrow" t "&rArr;" "=>" "=>" "⇒")
   >                             ("iff" "\\iff" t "&hArr;" "<=>" "<=>" "⇔")))

   > Hope this helps. 

Thanks for pointing out these settings, I will try them out.


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5556 bytes --]

  parent reply	other threads:[~2013-05-06  7:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05 17:45 org-preview-latex-fragment is very picky Uwe Brauer
2013-05-05 19:07 ` Rasmus
2013-05-05 20:01   ` Marcin Borkowski
2013-05-06  7:52   ` Uwe Brauer [this message]
2013-05-07 11:06   ` another example (was: org-preview-latex-fragment is very picky) Uwe Brauer
2013-05-07 11:44     ` another example Rasmus
2013-05-08 10:42       ` Uwe Brauer

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:

  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=87fvy05yus.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-orgmode@gnu.org \


* 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


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).