From: Max Nikulin <manikulin@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Tom Alexander <tom@fizz.buzz>, emacs-orgmode@gnu.org
Subject: Re: Inconsistent text markup handling when double-nesting markers
Date: Thu, 12 Oct 2023 17:23:09 +0700 [thread overview]
Message-ID: <86526a29-7792-4703-9961-243ebdbaa9fb@gmail.com> (raw)
In-Reply-To: <87ttqx73ay.fsf@localhost>
On 11/10/2023 19:26, Ihor Radchenko wrote:
> Max Nikulin writes:
>
>> P.S. Juan Manuel at certain moment discovered that pandoc allows nesting
>> for *b1 *b2* b3*.
>
> Which is a bug in pandoc.
>
> I think we discussed this topic a number of times in the past - our
> markup is a compromise between simplicity for users and simplicity of
> the parser. This works in many simple cases, but edge cases become
> problematic.
I have no intention to raise discussions of changing patterns to
recognize beginning and end of objects or extending of syntax.
My guess is that pandoc may use bottom-up, not top-down approach. I
admit, my opinion may be biased by reading complains concerning
unexpected behavior of current implementation. Perhaps besides
advantages pandoc parser has downsides. I would not be surprised if
bottom up parser is unbearable without some tool that generates code for
provided rules.
By the way, is it explicitly specified that within an element namely
top-down strategy must be used to recognize objects?
next prev parent reply other threads:[~2023-10-12 10:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 23:02 Inconsistent text markup handling when double-nesting markers Tom Alexander
2023-10-10 12:07 ` Ihor Radchenko
2023-10-11 2:23 ` Max Nikulin
2023-10-11 9:15 ` Ihor Radchenko
2023-10-11 12:16 ` Max Nikulin
2023-10-11 12:26 ` Ihor Radchenko
2023-10-11 14:40 ` Tom Alexander
2023-10-12 10:23 ` Max Nikulin [this message]
2023-10-12 12:04 ` Ihor Radchenko
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=86526a29-7792-4703-9961-243ebdbaa9fb@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tom@fizz.buzz \
--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).