GNU bug report logs - #78593
31.0.50; describe-key broken on interactive lambdas

Previous Next

Package: emacs;

Reported by: Madhu <enometh <at> meer.net>

Date: Mon, 26 May 2025 15:48:01 UTC

Severity: normal

Found in version 31.0.50

To reply to this bug, email your comments to 78593 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#78593; Package emacs. (Mon, 26 May 2025 15:48:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Madhu <enometh <at> meer.net>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Mon, 26 May 2025 15:48:02 GMT) Full text and rfc822 format available.

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

From: Madhu <enometh <at> meer.net>
To: bug-gnu-emacs <at> gnu.org
Subject: 31.0.50; describe-key broken on interactive lambdas
Date: Mon, 26 May 2025 21:16:22 +0530 (IST)
On recent master, but this seems to have been broken for a while:

$ emacs -Q -eval '(define-key global-map (kbd "<f11>") (lambda () (interactive) (bury-buffer)))'

C-h v <f11>

throws an error:

function-get: Wrong type argument: symbolp, #[nil ((bury-buffer)) (t) nil nil nil]

Acktually the *Help* buffer is formatted with sufficient information,
but the error prevents it from being displayed.

-- Madhu




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#78593; Package emacs. (Mon, 26 May 2025 16:47:01 GMT) Full text and rfc822 format available.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Madhu <enometh <at> meer.net>, Stefan Kangas <stefankangas <at> gmail.com>
Cc: 78593 <at> debbugs.gnu.org
Subject: Re: bug#78593: 31.0.50; describe-key broken on interactive lambdas
Date: Mon, 26 May 2025 19:46:21 +0300
> Date: Mon, 26 May 2025 21:16:22 +0530 (IST)
> From: Madhu <enometh <at> meer.net>
> 
> On recent master, but this seems to have been broken for a while:
> 
> $ emacs -Q -eval '(define-key global-map (kbd "<f11>") (lambda () (interactive) (bury-buffer)))'
> 
> C-h v <f11>
> 
> throws an error:
> 
> function-get: Wrong type argument: symbolp, #[nil ((bury-buffer)) (t) nil nil nil]
> 
> Acktually the *Help* buffer is formatted with sufficient information,
> but the error prevents it from being displayed.

Thanks.

Stefan, this is due to your change:

  commit a4ec9ca12969018cdf15b8cc713b3ba054326f99
  Author:     Stefan Kangas <stefankangas <at> gmail.com>
  AuthorDate: Tue Apr 1 21:25:33 2025 +0200
  Commit:     Stefan Kangas <stefankangas <at> gmail.com>
  CommitDate: Tue Apr 1 21:25:33 2025 +0200

      function-put: signal error with non-symbol

      * lisp/subr.el (function-get): Signal an error if given a non-symbol
      for consistency with 'get'.
      * test/lisp/subr-tests.el (subr-butlast): Test for the above.

Any reasons not to revert that?  function-get correctly returns nil if
its argument is not a symbol, so why should this signal an error?




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#78593; Package emacs. (Sat, 07 Jun 2025 08:41:01 GMT) Full text and rfc822 format available.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: stefankangas <at> gmail.com
Cc: 78593 <at> debbugs.gnu.org, enometh <at> meer.net
Subject: Re: bug#78593: 31.0.50; describe-key broken on interactive lambdas
Date: Sat, 07 Jun 2025 11:40:32 +0300
Ping!  Stefan, please chime in.

> Cc: 78593 <at> debbugs.gnu.org
> Date: Mon, 26 May 2025 19:46:21 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> 
> > Date: Mon, 26 May 2025 21:16:22 +0530 (IST)
> > From: Madhu <enometh <at> meer.net>
> > 
> > On recent master, but this seems to have been broken for a while:
> > 
> > $ emacs -Q -eval '(define-key global-map (kbd "<f11>") (lambda () (interactive) (bury-buffer)))'
> > 
> > C-h v <f11>
> > 
> > throws an error:
> > 
> > function-get: Wrong type argument: symbolp, #[nil ((bury-buffer)) (t) nil nil nil]
> > 
> > Acktually the *Help* buffer is formatted with sufficient information,
> > but the error prevents it from being displayed.
> 
> Thanks.
> 
> Stefan, this is due to your change:
> 
>   commit a4ec9ca12969018cdf15b8cc713b3ba054326f99
>   Author:     Stefan Kangas <stefankangas <at> gmail.com>
>   AuthorDate: Tue Apr 1 21:25:33 2025 +0200
>   Commit:     Stefan Kangas <stefankangas <at> gmail.com>
>   CommitDate: Tue Apr 1 21:25:33 2025 +0200
> 
>       function-put: signal error with non-symbol
> 
>       * lisp/subr.el (function-get): Signal an error if given a non-symbol
>       for consistency with 'get'.
>       * test/lisp/subr-tests.el (subr-butlast): Test for the above.
> 
> Any reasons not to revert that?  function-get correctly returns nil if
> its argument is not a symbol, so why should this signal an error?
> 
> 
> 
> 




This bug report was last modified 8 days ago.

Previous Next


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