From: "Rudolf Adamkovič" <rudolf@adamkovic.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: The less ambiguous math delimiters in tables
Date: Wed, 25 Dec 2024 21:14:07 +0100 [thread overview]
Message-ID: <m2msgj34hc.fsf@adamkovic.org> (raw)
In-Reply-To: <87r05vy6xq.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Your example shows ambiguous markup that can be
> interpreted in multiple ways:
>
> 1. <begin cell> \(<end cell><begin cell>x<end cell><begin cell>\) <end cell>
> 2. <begin cell> <begin latex>|x|<end latex> <end cell>
>
> Org parser chooses one. It has to choose some.
> Org parser also chooses a simpler interpretation that does not require
> backtracking.
But (2) is a *much, much, much* better choice (for the user).
How often does a table row contain
- a sole '\(` in one cell and
- a sole '\)` in another cell?
Virtually never [excluding verbatim/code, which is a different problem.]
How often does LaTeX include `|'? Often:
- absolute value,
- parallel lines,
- vector length,
- set cardinality,
- various norms,
on and on.
The use starts at elementary school level, so
it is like Org reserving the minus sign in LaTeX for itself,
which would be a similar usability disaster.
Rudy
--
"It is no paradox to say that in our most theoretical moods we may be
nearest to our most practical applications." --- Alfred North
Whitehead, 1861-1947
Rudolf Adamkovič <rudolf@adamkovic.org> [he/him]
http://adamkovic.org
next prev parent reply other threads:[~2024-12-25 20:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 9:20 The less ambiguous math delimiters in tables Rudolf Adamkovič
2024-12-24 9:25 ` Ihor Radchenko
2024-12-25 17:56 ` Rudolf Adamkovič
2024-12-25 18:05 ` Ihor Radchenko
2024-12-25 20:14 ` Rudolf Adamkovič [this message]
2024-12-26 9:17 ` Ihor Radchenko
2024-12-26 13:31 ` Rudolf Adamkovič
2024-12-26 13:51 ` Ihor Radchenko
2024-12-27 13:23 ` Rudolf Adamkovič
2024-12-27 13:35 ` Ihor Radchenko
2024-12-27 17:17 ` Leo Butler
2024-12-28 16:39 ` Max Nikulin
2024-12-24 9:50 ` Rudolf Adamkovič
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=m2msgj34hc.fsf@adamkovic.org \
--to=rudolf@adamkovic.org \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).