From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Org-mode <emacs-orgmode@gnu.org>, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Superscripts and subscripts
Date: Fri, 19 Apr 2013 20:20:52 +0200 [thread overview]
Message-ID: <87k3nynzzv.fsf@gmail.com> (raw)
In-Reply-To: <87d2tv3s5b.fsf@bzg.ath.cx> (Bastien's message of "Tue, 16 Apr 2013 08:29:20 +0200")
Hello,
Bastien <bzg@gnu.org> writes:
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> With a recent git pull and #+OPTIONS: ^:{}, `C^{14}' is interpreted
>> correctly but ` ^{14}C' is not, both in the Org buffer and in LaTeX
>> export. The space before the caret appears to be the problem.
>
> Confirmed -- this was reported already once. I don't have a fix for
> this at the moment, hopefully Nicolas can have a look sometime.
I made a non-whitespace character compulsory before the sub/superscript
marker a while ago, in order to circumvent a parsing problem.
Indeed, there is a parsing ambiguity between subscript and underline.
Consider the following example:
_example_
According to the syntax it can be either an underlined "example" string
or a subscript "example" string followed by an underscore string. Both
are valid interpretations.
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.
Suggestions welcome.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-04-19 18:20 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 [this message]
2013-04-19 18:52 ` Achim Gratz
2013-04-19 20:45 ` Thomas S. Dye
2013-04-20 5:26 ` Christian Moe
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:
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=87k3nynzzv.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.com \
/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).