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: Mon, 30 Dec 2024 22:02:31 +0100 [thread overview]
Message-ID: <m25xn0yjdk.fsf@adamkovic.org> (raw)
In-Reply-To: <87msgh5jwb.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> FYI, my approach to solve this problem is different - I want
> (eventually) to allow some kind of alternative syntax for tables that
> will allow bypassing similar situations. For example, we can allow
> multiple || to serve as delimiters:
>
> | this | is | a | normal | table | row |
> || here || we || allow || verbatim "|" || inside || ||
Your idea is not that different from what I proposed, except that it is
a less general, in that you special-case one particular problem with
tables. Or, would the "doubling escapes" work for all markup? Still,
that would not solve other table-related problems, such as
| =foo= and =bar= |,
where the problem is = and not |, right?
As for "parser bugs", I find it hard to believe that we could not come
up with some unambiguous sequence of characters, even if ugly, to
instruct the parser about precedence.
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-30 21:03 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
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č [this message]
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=m25xn0yjdk.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).