emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Christian Moe <mail@christianmoe.com>
Cc: Achim Gratz <Stromeko@nexgo.de>,
	emacs-orgmode@gnu.org, "Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Superscripts and subscripts
Date: Sat, 20 Apr 2013 21:11:10 +0200	[thread overview]
Message-ID: <87haj1kofl.fsf@gmail.com> (raw)
In-Reply-To: <m2vc7h93ii.fsf@christianmoe.com> (Christian Moe's message of "Sat, 20 Apr 2013 07:26:49 +0200")

Hello,

Christian Moe <mail@christianmoe.com> writes:

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

Simple: underline text was always handled (i.e. protected for further
transformation) before subscript.

But this doesn't remove the ambiguity. It just adds another parameter:
the parsing order.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-04-20 19:11 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
2013-04-20 19:11           ` Nicolas Goaziou [this message]
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=87haj1kofl.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \
    --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).