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

[GNU bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:56:13 +0000
with message-id <874jxok45u.fsf@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@gnu.org.)


-- 
57502: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57502
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 29.0.50; Issue with `or' clause of buffer-match-p
>
>
>
>
> Date: 
>
> Wed, 31 Aug 2022 14:02:46 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)
>
>
>
>
> 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))
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> 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@gnus.org> writes:
>
> > Philip Kaludercic <philipk@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.
>
>
> --- End Message ---