GNU bug report logs - #79455
"Value ‘1’ does not match type boolean" should mention which variable

Previous Next

Full log

Message #28 received at 79455 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: rdiez-2006 <at> rd10.de, 79455 <at> debbugs.gnu.org
Subject: Re: bug#79455: "Value ‘1’ does not match type
 boolean" should mention which variable
Date: Tue, 16 Sep 2025 18:45:50 +0300

> From: Robert Pluim <rpluim <at> gmail.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  79455 <at> debbugs.gnu.org
> Date: Tue, 16 Sep 2025 16:45:15 +0200
> 
> >>>>> On Tue, 16 Sep 2025 16:18:21 +0200, "R. Diez" <rdiez-2006 <at> rd10.de> said:
> 
>     R> [..]
>     >> Thanks, this is bug#73084, which is already fixed on the master branch
>     >> (which will eventually become Emacs 31).
> 
>     R> First of all, thanks for the info.
> 
>     R> That improvement was done over a year ago, and I hit this shortcoming the other day, after upgrading to the newest Emacs.
> 
>     R> It is a trivial change. Therefore, I wouldn't wait until Emacs 31, and
>     R> then let many users switching to Emacs 30.x (perhaps over a Linux
>     R> distribution package) unnecessarily scratch their heads.
> 
> Iʼm not sure there will ever be another release of Emacs 30.
> 
> Eli, I can backport 2ce0d397b12c to emacs-30 if you think it makes
> sense.

It doesn't make much sense, since we don't plan any more releases from
the emacs-30 branch.  And even if we do need to release from that
branch for some reason, this is not a bugfix, it's an enhancement.
Which is why it was done on the master branch to begin with.

Previous Next

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