emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: [RFC] Alternative to sub/superscript regexp
Date: Mon, 25 Nov 2013 18:14:27 +0100	[thread overview]
Message-ID: <87wqjw8kuk.fsf@gmail.com> (raw)


For the record `org-match-substring-regexp' is a variation on:

"\\(\\S-\\)\\([_^]\\)\\(\\(?:\\*\\|[-+]?[^-+*!@#$%^_ \t\r\n,:\"?<>~;./{}=()]+\\)\\)\\)"

I think it is a bit convoluted and therefore difficult to predict. For
example, as recent bug report showed, you may tend to interpret
a_b[fn:1] as


but, in fact, it is equivalent to


Of course, we can prevent this by forbidding "[" and "]" in the last
part of the regexp. But I wonder if there's something better to do.

The idea behind this regexp is that we should be able to write simple
sub/superscript, including numbers and entities, without requiring curly
braces (see `org-use-sub-superscripts' docstring for details). Maybe
something like the following could be an interesting alternative:


That is, without braces, either an asterisk or any combination of word,
number, dot, comma and backslash characters, which may start with either
a plus or a minus sign but cannot end with either a dot or a comma.

I find it arguably more predictable (no inverted class). Also, we "gain"
the following:

  a^3.14. <=> a^{3.14}.

At the moment, a^3.14. <=> a^{3}.14.

What do you think?


Nicolas Goaziou

             reply	other threads:[~2013-11-25 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 17:14 Nicolas Goaziou [this message]
2013-11-25 17:45 ` [RFC] Alternative to sub/superscript regexp Nick Dokos
2013-11-25 21:53 ` Rasmus
2013-11-26  9:20 ` Carsten Dominik
2013-11-26 16:46   ` Nicolas Goaziou
2013-12-18 22:13     ` Nicolas Goaziou
2014-01-11 23:18       ` 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=87wqjw8kuk.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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