From: Robert Goldman <rpgoldman@sift.info>
To: emacs-orgmode@gnu.org
Subject: Re: Two questions about latex export
Date: Mon, 27 Apr 2009 13:35:00 -0500 [thread overview]
Message-ID: <49F5FAD4.5010504@sift.info> (raw)
In-Reply-To: <49F5ECAC.4040700@sift.info>
Robert Goldman wrote:
> 1. I am making a table of conditional probabilities. This means the
> table headers look like this: p(e|\omega), for example. The vbar in the
> header confuses orgmode. It thinks that's a column-delimiter. Adding a
> prefix \ does not help. Is there a work around? For the moment I put
> \newcommand{\vbar}{|} in a latex block and use \vbar in place of |.
> Works, but makes the table a little less readable than I'd like.
>
> more importantly:
>
> 2. I put an eqnarray* environment in my org file. The equation breaks
> across multiple lines so it looks like this:
>
> \begin{eqnarray*}
>
> x &=& blah blah blah \\
> &=& blah blah blah \\
> &=& blah blah blah \\
> \end{eqnarray*}
>
> org-mode quotes (backslashes) the &=& so they don't get interpreted
> correctly. Is there something I can do to keep that from happening?
A quick follow up to this one. The bug does NOT occur if I substitute
eqnarray for eqnarray*. I believe that this means that the constant
org-latex-entities in org-latex.el needs to be modified to admit the
starred (unnumbered) variants of the latex math operators.
Unfortunately, my simple-minded attempt to butcher in stars has run
aground on the shoals of my ignorance of the combination of emacs-lisp
string escapes, and emacs regexpressions. Simply adding
"\\begin{eqnarray*}"
to that list won't work, and even
"\\begin{eqnarray\\*}"
doesn't seem to do the right thing. if anyone can put me on the right
track, I'll try to provide a patch.
Thanks!
next prev parent reply other threads:[~2009-04-27 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 17:34 Two questions about latex export Robert Goldman
2009-04-27 18:35 ` Robert Goldman [this message]
2009-04-29 19:37 ` Carsten Dominik
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49F5FAD4.5010504@sift.info \
--to=rpgoldman@sift.info \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.