GNU bug report logs - #57502
29.0.50; Issue with `or' clause of buffer-match-p

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#57502: closed (29.0.50; Issue with `or' clause of buffer-match-p)
Date: Sat, 03 Sep 2022 12:57:01 +0000

[Message part 1 (text/plain, inline)]

Your message dated Sat, 03 Sep 2022 12:56:13 +0000
with message-id <874jxok45u.fsf <at> posteo.net>
and subject line Re: bug#57502: 29.0.50; Issue with `or' clause of buffer-match-p
has caused the debbugs.gnu.org bug report #57502,
regarding 29.0.50; Issue with `or' clause of buffer-match-p
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
57502: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57502
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Augusto Stoffel <arstoffel <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.0.50; Issue with `or' clause of buffer-match-p
Date: Wed, 31 Aug 2022 14:02:46 +0200

This buffer-match-p condition does the expected job:

     (buffer-match-p '(or "\\*" (derived-mode . special-mode))
                     (current-buffer))

But this presumably equivalent one gives a “(wrong-type-argument listp
special-mode)” error:

     (buffer-match-p '(or (and "\\*")
                          (derived-mode . special-mode))
                     (current-buffer))

[Message part 3 (message/rfc822, inline)]

From: Philip Kaludercic <philipk <at> posteo.net>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 57502-done <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 arstoffel <at> gmail.com
Subject: Re: bug#57502: 29.0.50; Issue with `or' clause of buffer-match-p
Date: Sat, 03 Sep 2022 12:56:13 +0000

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> Philip Kaludercic <philipk <at> posteo.net> writes:
>
>> So unless there is a plan to revert this trend, I'd use pcase to avoid
>> simple issues like the one that caused this bug.
>
> Looks good to me.

Ok, I've pushed the change.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.