From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Two questions about latex export Date: Wed, 29 Apr 2009 21:37:35 +0200 Message-ID: <45CE9A8E-5416-47E0-8196-1BBFAD6DC7DB@gmail.com> References: <49F5ECAC.4040700@sift.info> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M0eKM-00046O-VR for emacs-orgmode@gnu.org; Sun, 03 May 2009 12:14:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M0eKI-000441-5G for emacs-orgmode@gnu.org; Sun, 03 May 2009 12:14:06 -0400 Received: from [199.232.76.173] (port=45919 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M0eKH-00043x-Vs for emacs-orgmode@gnu.org; Sun, 03 May 2009 12:14:02 -0400 Received: from mail-ew0-f162.google.com ([209.85.219.162]:50067) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M0eKH-0002RR-MT for emacs-orgmode@gnu.org; Sun, 03 May 2009 12:14:01 -0400 Received: by mail-ew0-f162.google.com with SMTP id 6so3488352ewy.42 for ; Sun, 03 May 2009 09:14:01 -0700 (PDT) In-Reply-To: <49F5ECAC.4040700@sift.info> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Robert Goldman Cc: emacs-orgmode@gnu.org On Apr 27, 2009, at 7:34 PM, 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. \vert, as pointed out by Giovanni. > > 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? This is a bug, fixed now, thanks. - Carsten