emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: latex fragment problems with * environments
Date: Mon, 11 May 2009 19:02:29 +0100	[thread overview]
Message-ID: <87bppzbjre.fsf@eeepc.chemeng.ucl.ac.uk> (raw)

Carsten et al.,

If I have the following bit of LaTeX code in my org file:

|   \begin{eqnarray}
|     x &=& a_i + b_j + c_{k} \\
|     y &=& \sqrt{x}
|   \end{eqnarray}
|   \begin{eqnarray*}
|     x &=& a_i + b_j + c_{k} \\
|     y &=& \sqrt{x}
|   \end{eqnarray*}

and ask for a LaTeX export, I get the following generated:

|   \begin{eqnarray}
|     x &=& a_i + b_j + c_{k} \\
|     y &=& \sqrt{x}
|   \end{eqnarray}
|   \begin{eqnarray*}
|     x \&=\& a$_i$ + b$_j$ + c$_{k}$ \\
|     y \&=\& \sqrt{x}
|   \end{eqnarray*}

The second environment has not been recognised by org-mode as a valid
latex fragment and so all the special characters (&, _) have been
processed instead of being left alone.  

This could be my fault but I have no idea where to start looking in case
I've set something I shouldn't have.  Because the latex exporter has
changed since I last used any latex fragments in my org files, and that
has been a while, I am not sure if this ever worked properly anyway.

Or it could be that "*" environments don't get recognised correctly by
the latex exporter?  Is there a regexp that I can customise for this?

Thanks for any suggestions!  I've temporarily changed all * environments
to ones with the * (so I get tons of equation numbers I don't need) but
I would love to revert to what I had originally.


             reply	other threads:[~2009-05-11 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 18:02 Eric S Fraga [this message]
2009-05-11 20:52 ` latex fragment problems with * environments Carsten Dominik
2009-05-12 10:07   ` Eric S Fraga, Eric S Fraga
2009-05-12 10:29     ` Carsten Dominik
2009-05-12 10:34       ` Eric S Fraga, Eric S Fraga

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=87bppzbjre.fsf@eeepc.chemeng.ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).