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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: "R. Diez" <rdiez-2006 <at> rd10.de>
Cc: rpluim <at> gmail.com, 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:43:11 +0300

> X-Spam-Status: No, score=-2.901 required=6.31 tests=[ALL_TRUSTED=-1,
> 	BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
> Date: Tue, 16 Sep 2025 16:18:21 +0200
> Cc: 79455-done <at> debbugs.gnu.org, Robert Pluim <rpluim <at> gmail.com>
> From: "R. Diez" <rdiez-2006 <at> rd10.de>
> 
> [..]
> > Thanks, this is bug#73084, which is already fixed on the master branch
> > (which will eventually become Emacs 31).
> 
> First of all, thanks for the info.
> 
> That improvement was done over a year ago, and I hit this shortcoming the other day, after upgrading to the newest Emacs.
> 
> It is a trivial change. Therefore, I wouldn't wait until Emacs 31, and then let many users switching to Emacs 30.x (perhaps over a Linux distribution package) unnecessarily scratch their heads.

Sorry, our rule is no enhancements on the release branch.  We paid
with sweat, blood, and tears to learn that simple truth.

You can always apply that change locally and rebuild Emacs 30 for your
needs.

Previous Next

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