From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robert Goldman <rpgoldman@sift.info>
Subject: Re: Two questions about latex export
Date: Mon, 27 Apr 2009 13:35:00 -0500
Message-ID: <49F5FAD4.5010504@sift.info>
References: <49F5ECAC.4040700@sift.info>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LyVnj-0007mJ-A2
	for emacs-orgmode@gnu.org; Mon, 27 Apr 2009 14:43:35 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LyVne-0007jk-LY
	for emacs-orgmode@gnu.org; Mon, 27 Apr 2009 14:43:35 -0400
Received: from [199.232.76.173] (port=49282 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LyVne-0007jb-EL
	for emacs-orgmode@gnu.org; Mon, 27 Apr 2009 14:43:30 -0400
Received: from outbound-mail-06.bluehost.com ([69.89.17.206]:49821)
	by monty-python.gnu.org with smtp (Exim 4.60)
	(envelope-from <rpgoldman@sift.info>) id 1LyVnd-0008QV-UF
	for emacs-orgmode@gnu.org; Mon, 27 Apr 2009 14:43:30 -0400
In-Reply-To: <49F5ECAC.4040700@sift.info>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

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!