all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Sean Devlin <spd@toadstyle.org>
Cc: Helmut Eller <eller.helmut@gmail.com>, 59345@debbugs.gnu.org
Subject: bug#59345: 28.2; peg.el: syntax-class PEX does not advance point
Date: Fri, 18 Nov 2022 07:16:38 +0100	[thread overview]
Message-ID: <875yfcokhl.fsf@web.de> (raw)
In-Reply-To: <16D8C25F-31A8-44D8-9DDC-3CFF149183C2@toadstyle.org> (Sean Devlin's message of "Thu, 17 Nov 2022 18:49:20 -0500")

Sean Devlin <spd@toadstyle.org> writes:

> In version 1.0 of peg.el, there is a PEX to match the syntax class of
> the character at point. I expected it to advance the point after
> recognizing the correct class, but it seems that it does not.

Yes, I too think this is a bug.

PEGs that match something after the char class matching part even fail,
which is definitely not correct: compare in a buffer containing "  a":

  (peg-run (peg (* [blank]) "a"))

vs.

  (peg-run (peg (* (syntax-class whitespace)) "a"))

The fist one matches up to the "a", the seconds doesn't, but should.

I CC Helmut Eller, the author of peg.el.


Michael.





  reply	other threads:[~2022-11-18  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 23:49 bug#59345: 28.2; peg.el: syntax-class PEX does not advance point Sean Devlin
2022-11-18  6:16 ` Michael Heerdegen [this message]
2022-11-28  8:32   ` Helmut Eller
2022-11-28  8:55     ` Michael Heerdegen
2022-11-28 16:58       ` Eric Abrahamsen
2022-11-28 22:40         ` Eric Abrahamsen
2022-11-28 22:50           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-29  9:46           ` Michael Heerdegen
2022-11-29 16:11             ` Eric Abrahamsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yfcokhl.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=59345@debbugs.gnu.org \
    --cc=eller.helmut@gmail.com \
    --cc=spd@toadstyle.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.