emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: org-preview-latex-fragment is very picky
Date: Sun, 05 May 2013 21:07:23 +0200	[thread overview]
Message-ID: <87mws9z1n8.fsf@pank.eu> (raw)
In-Reply-To: 87ip2xqq0d.fsf@mat.ucm.es

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

> Hello 
> the following formula works well with org-preview-latex-fragment
> $\|v^k(t
> However 
> $ \|vk(t)\|_{Hs+1,δ}$
> Not nor 
> $ \|vk(t)\|_{Hs+1,δ}$,
> Could that behaviour made a little less picky?

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. 


Don't panic!!!

  reply	other threads:[~2013-05-05 19:07 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 [this message]
2013-05-05 20:01   ` Marcin Borkowski
2013-05-06  7:52   ` Uwe Brauer
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=87mws9z1n8.fsf@pank.eu \
    --to=rasmus@gmx.us \
    --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).