From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mattias Newsgroups: gmane.emacs.bugs Subject: bug#71510: 30.0.50; kill-this-buffer must be bound to an event with parameters Date: Wed, 12 Jun 2024 14:51:48 +0200 Message-ID: References: <86bk461lf5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11573"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla Thunderbird Cc: 71510@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jun 13 07:24:34 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sHcwr-0002qD-RU for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 13 Jun 2024 07:24:33 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sHcwR-0007Vi-LU; Thu, 13 Jun 2024 01:24:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sHcwQ-0007VM-5G for bug-gnu-emacs@gnu.org; Thu, 13 Jun 2024 01:24:06 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sHcwP-0004rv-T7 for bug-gnu-emacs@gnu.org; Thu, 13 Jun 2024 01:24:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sHcwP-0007IZ-4y for bug-gnu-emacs@gnu.org; Thu, 13 Jun 2024 01:24:05 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mattias Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 13 Jun 2024 05:24:05 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71510 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 71510-submit@debbugs.gnu.org id=B71510.171825622327898 (code B ref 71510); Thu, 13 Jun 2024 05:24:05 +0000 Original-Received: (at 71510) by debbugs.gnu.org; 13 Jun 2024 05:23:43 +0000 Original-Received: from localhost ([127.0.0.1]:51681 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sHcw2-0007Fp-4i for submit@debbugs.gnu.org; Thu, 13 Jun 2024 01:23:43 -0400 Original-Received: from smtp5-g21.free.fr ([212.27.42.5]:3818) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sHNSe-0001PL-9V for 71510@debbugs.gnu.org; Wed, 12 Jun 2024 08:52:21 -0400 Original-Received: from [IPV6:2a01:e0a:b97:f2e0:a32:c761:ed2:1fb3] (unknown [IPv6:2a01:e0a:b97:f2e0:a32:c761:ed2:1fb3]) (Authenticated sender: mattias.roux@free.fr) by smtp5-g21.free.fr (Postfix) with ESMTPSA id 74D4F60142; Wed, 12 Jun 2024 14:51:49 +0200 (CEST) Content-Language: en-US In-Reply-To: <86bk461lf5.fsf@gnu.org> X-Mailman-Approved-At: Thu, 13 Jun 2024 01:23:40 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:287175 Archived-At: Hi Eli, Thanks for your answer. To make it clear, I don't pretend that it's a bug, I just noticed that the previous behaviour is no longer maintained. The doc associated to the function states that:     When called in the minibuffer, get out of the minibuffer     using `abort-recursive-edit'.     This command can be reliably invoked only from the menu bar,     otherwise it could decide to silently do nothing." So it looks like now the behaviour is enforced but the error message is a bit underwhelming and the error trace doesn't help to understand what's happening. Anyway, thanks a lot for your answer, I'll now use `kill-current-buffer` Mattias Le 12/06/2024 à 12:54, Eli Zaretskii a écrit : > tags 71510 notabug > thanks > >> Date: Wed, 12 Jun 2024 11:06:36 +0200 >> From: Mattias >> >> >> 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.