From: Timothy <firstname.lastname@example.org>
To: "Rudolf Adamkovič" <email@example.com>
Cc: Max Nikulin <firstname.lastname@example.org>, email@example.com
Subject: Re: [PATCH v2] org-manual.org: $n$-th is not math
Date: Wed, 22 Mar 2023 20:37:48 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
> Funny, I the exact opposite of you; I would pay many to see $…$th and
> $…$-th special-cased (with tests, so that it would not break again).
I feel the need to point out that this way lies madness.
The behaviour of $ in Org is /inherrently/ confusing. You’re confused by `$...$th'
and `$...$-th'. Say those were special-cased, somebody notices the work and then
try `$n$-dimensional' and now are /even more confused/ when it doesn’t work.
Ok, say we make `$...$' just apply in more cases, then we have somebody who
writing about prices who changed `$3 or =$5' to `$3-$5' and now “weird things are
The root issue is the way that `$' tries to pull double-duty as both a literal `$'
and a delimiter. It’s all very well to say that “in LaTeX this is fine”, however
in LaTeX this /simply is not an issue/* as single dollars must be escaped as `\$'.
We can fiddle with the heuristics, but there is no perfect solution here …
other than to move away from `$' and prioritise `\( ... \)' in our documentation and
examples, even add a linter rule that raises warnings about the tendency of
dollar-math to misbehave when people use it.
All the best,
* It’s still a pain/discouraged for other reasons.
Timothy (‘tecosaur’/‘TEC’), Org mode contributor.
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/tec>.
next prev parent reply other threads:[~2023-03-22 13:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 13:32 [PATCH] org-manual.org: $n$-th is not math Max Nikulin
2023-03-15 14:01 ` Loris Bennett
2023-03-15 17:25 ` Rudolf Adamkovič
2023-03-17 12:13 ` [PATCH v2] " Max Nikulin
2023-03-18 12:21 ` Ihor Radchenko
2023-03-19 11:08 ` Rudolf Adamkovič
2023-03-19 11:24 ` Ihor Radchenko
2023-03-19 15:18 ` Max Nikulin
2023-03-21 16:38 ` Rudolf Adamkovič
2023-03-22 11:47 ` Max Nikulin
2023-03-22 12:37 ` Timothy [this message]
2023-03-22 17:17 ` Rudolf Adamkovič
2023-03-23 12:03 ` Ihor Radchenko
2023-03-23 21:51 ` Rudolf Adamkovič
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 \
* 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).