From: Robert Goldman <rpgoldman@sift.info>
To: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Two questions about latex export
Date: Tue, 28 Apr 2009 08:46:28 -0500 [thread overview]
Message-ID: <49F708B4.5080206@sift.info> (raw)
In-Reply-To: <615735.24159.qm@web28306.mail.ukl.yahoo.com>
Giovanni Ridolfi wrote:
> --- Lun 27/4/09, Robert Goldman <rpgoldman@sift.info> ha scritto:
>>> 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.
>
> \vert
Thanks! That fixed my problem! Strangely, \vert doesn't appear in The
Latex Companion (or at least not in its index).
>
>>> more importantly:
>>>
>>> 2. I put an eqnarray* environment in my org
>>> file.
>
> #+BEGIN_LaTeX
>
> \begin{eqnarray}
> \label{integralpha293}
>
> \alpha=\Gamma
>
> \end{eqnarray}
>
> #+END_LaTeX
Two answers:
1. eqnarray *without* the BEGIN and END blocks works. I believe that
this is because org-mode "knows" eqnarray, but not eqnarray*. I am
inclined to think that this is a buglet, and we should put support for
eqnarray* into org-mode.
2. I don't believe that the BEGIN and END blocks approach is
equivalent. If I understand correctly, the use of these BEGIN and END
blocks says "put this in only when I am exporting to Latex." From the
manual: "...you can add special code
that should only be present in LaTeX export with the following
constructs: [#+LaTeX and #+BEGIN_LaTeX ... #+END_LaTeX]."
Adding those delimiters changes the meaning of my document. *Without*
those delimiters, my equation goes in an HTML or ASCII export (in some
form); with those delimiters, the equation will only be exported when
exporting to LaTeX....
Best,
Robert
prev parent reply other threads:[~2009-04-28 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 8:06 Re: Two questions about latex export Giovanni Ridolfi
2009-04-28 13:46 ` Robert Goldman [this message]
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=49F708B4.5080206@sift.info \
--to=rpgoldman@sift.info \
--cc=emacs-orgmode@gnu.org \
--cc=giovanni.ridolfi@yahoo.it \
/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).