From: Nick Dokos <nicholas.dokos@hp.com>
To: Peter Rayner <prayner@unimelb.edu.au>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: overruling subscripts in latex export
Date: Tue, 24 Jan 2012 23:27:08 -0500 [thread overview]
Message-ID: <3285.1327465628@alphaville> (raw)
In-Reply-To: Message from Peter Rayner <prayner@unimelb.edu.au> of "Wed, 25 Jan 2012 13:02:12 +1100." <20255.25252.403452.217345@raynernix2.earthsci.unimelb.edu.au>
Peter Rayner <prayner@unimelb.edu.au> wrote:
> I'm documenting some code including lists of parameters. These have
> underscores in them which I don't want to interpret as subscripts.
> According to the manual I can overrule this behaviour with an option
> but it looks like I'm doing something wrong.
>
> Here is the test file
> #+OPTIONS: ^:{}
> #+TITLE: test file
>
> - p_c_in :: this is the first parameter
> - g_c_in :: and this is the second
>
>
> ...
>
>
> \begin{description}
> \item[p$_c$$_{\mathrm{in}}$] this is the first parameter
> \item[g$_c$$_{\mathrm{in}}$] and this is the second
> \end{description}
>
I get
,----
| \begin{description}
| \item[p\_{}c\_{}in] this is the first parameter
| \item[g\_{}c\_{}in] and this is the second
| \end{description}
`----
which is what's expected. It might be that you didn't update the setup
of the buffer after you added the #+OPTIONS line (just press C-c C-c on
it). Equivalently, kill the buffer and find-file again: the option should
be active.
Assuming of course that you have a reasonably modern version of org. Mine is
Org-mode version 7.8.03 (release_7.8.03.230.g67cb2.dirty)
(which includes a few local patches)
Nick
next prev parent reply other threads:[~2012-01-25 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 2:02 overruling subscripts in latex export Peter Rayner
2012-01-25 4:27 ` Nick Dokos [this message]
2012-01-25 4:54 ` Peter Rayner
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=3285.1327465628@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=prayner@unimelb.edu.au \
/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).