emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: Superscripts and subscripts
Date: Sat, 20 Apr 2013 07:26:49 +0200	[thread overview]
Message-ID: <m2vc7h93ii.fsf@christianmoe.com> (raw)
In-Reply-To: <m1zjwu45da.fsf@poto.westell.com>

>> Nicolas Goaziou writes:
>>> Of course, we could work around this with a new rule saying "the longest
>>> match wins", which, in this case, is the underline. But it would be
>>> better to find a more elegant solution, one which would remove the sole
>>> ambiguity, AFAICT, in Org syntax.

How did this work before? I never tried subscript after whitespace. But
we had both superscript-after-whitespace and
underlining-with-underscores working at the same time, without the
ambiguity causing problems as far as I remember.

Indeed, it's very difficult to think of a case where wrapping something
in underscores should not mean underline because you'd want subscript or
superscript before and underscore after.

Though I'm sure there's an Org user out there with a use case. :)

> Achim Gratz <Stromeko@nexgo.de> writes:
>> How about {}^{14}C or {^{14}}C?

Works for me, I guess, if it has to be.

Thomas S. Dye writes:
> The LaTeX solution, which recognizes the superscript and subscript
> symbols in math mode, would only require a change in the Org
> documentation.  This works: \(^{14}\)C.

Yep, but in non-latex backends, a superscript that's native to the
backend would be a happier solution.


  reply	other threads:[~2013-04-20  5:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 21:07 Superscripts and subscripts Thomas S. Dye
2013-04-16  6:29 ` Bastien
2013-04-18  2:57   ` Daniel Mahler
2013-04-18  3:18     ` John Hendy
2013-04-18  3:54       ` Daniel Mahler
2013-04-18  8:00         ` Daniel Mahler
2013-04-19 18:20   ` Nicolas Goaziou
2013-04-19 18:52     ` Achim Gratz
2013-04-19 20:45       ` Thomas S. Dye
2013-04-20  5:26         ` Christian Moe [this message]
2013-04-20 19:11           ` Nicolas Goaziou
2013-04-20 19:19       ` Nicolas Goaziou

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:

  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=m2vc7h93ii.fsf@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.com \


* 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


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).