From: Ihor Radchenko <yantar92@posteo.net>
To: "Rudolf Adamkovič" <rudolf@adamkovic.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: The less ambiguous math delimiters in tables
Date: Wed, 25 Dec 2024 18:05:21 +0000 [thread overview]
Message-ID: <87r05vy6xq.fsf@localhost> (raw)
In-Reply-To: <m2pllf3aum.fsf@adamkovic.org>
Rudolf Adamkovič <rudolf@adamkovic.org> writes:
>> It is a syntax limitation.
>> Org parser is outer-inner - the table row is parsed first.
>> So, | are unconditionally used as table delimiters, *before* verbatim
>> LaTeX markup is recognized.
>
> How is that not a parser bug?
>
> I thought that, with the noisy \(...\) delimiters,
>
> the parser finally has enough information
>
> to not screw up.
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.
> P.S. It is impossible to write, e.g. \|, which is vector length (norm).
Yes, it is impossible. That's why I call it markup limitation.
We need to improve the markup to address this known problematic scenario.
--
Ihor Radchenko // yantar92,
Org mode maintainer,
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/yantar92>
next prev parent reply other threads:[~2024-12-25 18:04 UTC|newest]
Thread overview: 25+ 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 [this message]
2024-12-25 20:14 ` Rudolf Adamkovič
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-30 21:02 ` Rudolf Adamkovič
2024-12-31 17:47 ` Ihor Radchenko
2024-12-27 17:17 ` Leo Butler
2024-12-28 16:39 ` Max Nikulin
2024-12-30 21:25 ` Rudolf Adamkovič
2025-01-02 17:02 ` Max Nikulin
2024-12-31 5:43 ` Ihor Radchenko
2024-12-31 12:20 ` Rudolf Adamkovič
2024-12-31 13:32 ` Ihor Radchenko
2024-12-31 15:57 ` Rudolf Adamkovič
2024-12-31 16:46 ` Ihor Radchenko
2025-01-02 17:20 ` Max Nikulin
2025-01-02 17:32 ` Ihor Radchenko
2025-01-03 15:14 ` 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=87r05vy6xq.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=rudolf@adamkovic.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).