From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christian Moe <mail@christianmoe.com>
Subject: Re: Superscripts and subscripts
Date: Sat, 20 Apr 2013 07:26:49 +0200
Message-ID: <m2vc7h93ii.fsf@christianmoe.com>
References: <m14nf7bj0i.fsf@poto.westell.com> <87d2tv3s5b.fsf@bzg.ath.cx>
	<87k3nynzzv.fsf@gmail.com> <877gjy9wvg.fsf@Rainer.invalid>
	<m1zjwu45da.fsf@poto.westell.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:43084)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1UTQHS-0008Em-03
	for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 01:24:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1UTQHQ-00039N-TG
	for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 01:24:09 -0400
Received: from mail2.b1.hitrost.net ([91.185.211.205]:27251)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@christianmoe.com>) id 1UTQHQ-000397-M3
	for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 01:24:08 -0400
In-reply-to: <m1zjwu45da.fsf@poto.westell.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org


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

Yours,
Christian