From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: latex fragment problems with * environments
Date: Mon, 11 May 2009 22:52:19 +0200 [thread overview]
Message-ID: <545921C6-2249-45B7-812B-225AE4113987@gmail.com> (raw)
In-Reply-To: <87bppzbjre.fsf@eeepc.chemeng.ucl.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1904 bytes --]
Hi Eric,
this was fixed 11 days ago in commit
5f86fd7ae2da40b20c967382fa938fc871fb7e44
If you use the latet git version, this problem will not be present.
- Carsten
On May 11, 2009, at 8:02 PM, Eric S Fraga wrote:
> 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.
>
> eric
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[-- Attachment #1.2: Type: text/html, Size: 2646 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2009-05-11 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 18:02 latex fragment problems with * environments Eric S Fraga
2009-05-11 20:52 ` Carsten Dominik [this message]
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:
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=545921C6-2249-45B7-812B-225AE4113987@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).