From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: acorallo@gnu.org, 74018@debbugs.gnu.org
Subject: bug#74018: 31.0.50; Issue with define-peg-ruleset?
Date: Mon, 28 Oct 2024 15:54:53 -0700 [thread overview]
Message-ID: <CADwFkmndgKrjyaF=DuazjnLWym9ra2sGbF6KLrGWBad2FicmXg@mail.gmail.com> (raw)
In-Reply-To: <86ldya50ia.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Cc: Stefan Kangas <stefankangas@gmail.com>, Andrea Corallo
>> <acorallo@gnu.org>, 74018@debbugs.gnu.org
>> Date: Sat, 26 Oct 2024 10:24:33 -0400
>>
>> >> I was about to install the bugfix below to `master` but noticed that it
>> >> probably belongs to `emacs-30` instead since the bug makes
>> >> `define-peg-ruleset` basically unusable and PEG is new in Emacs-30.
>> >>
>> >> Any objection?
>> >
>> > I know nothing about peg.el, and you haven't explained the root cause
>> > for the bug for me to understand why it "makes `define-peg-ruleset'
>> > basically unusable", so let's hear from Stefan and Andrea first.
>>
>> Here's a more complete description.
>
> Thanks. Andrea already agreed with installing this on the release
> branch. I hope Stefan Kangas will respond soon.
No objections from me either, please go ahead.
next prev parent reply other threads:[~2024-10-28 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 20:30 bug#74018: 31.0.50; Issue with define-peg-ruleset? Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-25 21:01 ` Andrea Corallo
2024-10-26 6:16 ` Eli Zaretskii
2024-10-26 14:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 15:47 ` Eli Zaretskii
2024-10-28 22:54 ` Stefan Kangas [this message]
2024-10-29 2:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmndgKrjyaF=DuazjnLWym9ra2sGbF6KLrGWBad2FicmXg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=74018@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.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).