Subject: bug#57502: closed (Re: bug#57502: 29.0.50; Issue with `or' clause of buffer-match-p)

From: [email-masked] (GNU bug Tracking System)
Date: Sat, 03 Sep 2022 12:57:02 +0000

Your bug report

#57502: 29.0.50; Issue with `or' clause of buffer-match-p

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
57502: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57502
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#57502: 29.0.50; Issue with `or' clause of buffer-match-p
From: Philip Kaludercic <[email-masked]>
To: Lars Ingebrigtsen <[email-masked]>
Cc: [email-masked], Eli Zaretskii <[email-masked]>, [email-masked]
Date: Sat, 03 Sep 2022 12:56:13 +0000
List-Id: <debbugs-submit.debbugs.gnu.org>

Lars Ingebrigtsen <[email-masked]> writes:

> Philip Kaludercic <[email-masked]> 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.

Subject: 29.0.50; Issue with `or' clause of buffer-match-p
From: Augusto Stoffel <[email-masked]>
To: [email-masked]
Date: Wed, 31 Aug 2022 14:02:46 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

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))