From: heroxbd@gentoo.org
To: emacs-orgmode@gnu.org
Subject: syntax specification (was Re: Bug: [regression] superscript not available after non-alphanumeric)
Date: Sat, 28 Jun 2014 10:39:09 +0900 [thread overview]
Message-ID: <86fvipols2.fsf_-_@moguhome00.in.awa.tohoku.ac.jp> (raw)
In-Reply-To: <878uoiy3bd.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 27 Jun 2014 13:55:34 +0200")
Hi Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> If you want to insert raw LaTeX in an Org buffer, then \ce{^{238}U} is
> invalid because you cannot nest braces. You can write instead:
>
> @@latex:\ce{^{238}U}@@
>
> or you can define a macro, e.g.,:
>
> #+MACRO: ce @@latex:\ce{$1}@@
>
> and then use
>
> {{{ce(^{238}U)}}}
>
> Also, ^2H is not recognized as superscript _on purpose_. Per Org syntax,
> you have to add a non-blank character before the caret. Otherwise, there
> would be ambiguity between underline (e.g., _under_) and subscript
> (_under). And superscript syntax follows subscript's.
>
> In this case, you can probably use a math snippet, e.g.,
>
> \(^2\)H
Thank you for the explanation. I got to know what went wrong.
I am wondering where the claims "you cannot nest braces" and "Per Org
syntax, you have to add a non-blank character before the caret" come
from. Is there a general principle guideline for the org syntax, or is
it a taste of the maintainer only?
Is it true when an exporter maintainer changes, the syntax changes to
his somehow incompatible preference? In [1], Carsten regarded "you have
to add a non-blank character before the caret" as a bug and fixed it;
while you regard it as a rule. I am curious about what was the
compelling motivation to make this shift.
Interpreting \ce{^{238}U} directly complicates the exporter parser
logic, while gives LaTeX composers a syntax sugar. The inconvenience of
"\(^2\)H" is similar to "\_leading_under_line". Either syntax is not
superior to the other. Maintaining a stable syntax is the principle in
this case.
Don't get me wrong. I appreciate and respect your new-school exporting
framework, and the sexy features it makes possible. I am to express my
value and concern on the longterm specification (and consequently
usability) of the org syntax.
Cheers,
Benda
1. http://lists.gnu.org/archive/html/emacs-orgmode/2009-09/msg00887.html
next prev parent reply other threads:[~2014-06-28 1:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-27 10:42 Bug: [regression] superscript not available after non-alphanumeric [8.2.7b (8.2.7b-dist @ /home/benda/gnto/usr/share/emacs/site-lisp/org-mode/)] heroxbd
2014-06-27 11:55 ` Nicolas Goaziou
2014-06-28 1:39 ` heroxbd [this message]
2014-06-29 11:47 ` [PATCH] curly nested latex fragments (was: superscript not available after non-alphanumeric) heroxbd
2014-06-29 13:53 ` [PATCH] curly nested latex fragments Nicolas Goaziou
2014-06-30 0:38 ` heroxbd
2014-06-30 12:31 ` Nicolas Goaziou
2014-06-30 21:50 ` heroxbd
2014-07-06 20:11 ` 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=86fvipols2.fsf_-_@moguhome00.in.awa.tohoku.ac.jp \
--to=heroxbd@gentoo.org \
--cc=emacs-orgmode@gnu.org \
/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).