GNU bug report logs - #71510
30.0.50; kill-this-buffer must be bound to an event with parameters

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mattias <mattias <at> kojin.tech>
Cc: 71510 <at> debbugs.gnu.org
Subject: Re: bug#71510: 30.0.50;
 kill-this-buffer must be bound to an event with parameters
Date: Wed, 12 Jun 2024 13:54:06 +0300

tags 71510 notabug
thanks

> Date: Wed, 12 Jun 2024 11:06:36 +0200
> From: Mattias <mattias <at> kojin.tech>
> 
> 
> kill-this-buffer is not working as before anymore.
> 
> Old behaviour:
> 
> e -Q
> C-x 3
> M-x kill-this-buffer
> 
> would kill the current buffer and display only one frame
> 
> e -Q
> C-x 3
> M-x kill-this-buffer
> 
> Will raise an error:
> 
> Debugger entered--Lisp error: (error "kill-this-buffer must be bound to 
> an event with parameters")
> command-execute(kill-this-buffer record)
> execute-extended-command(nil "kill-this-buffer" "kill-th")
> funcall-interactively(execute-extended-command nil "kill-this-buffer" 
> "kill-th")
> command-execute(execute-extended-command)

This is the intended behavior, not a bug: this command must be invoked
from a mouse event.

Previous Next

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