From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71510@debbugs.gnu.org, Mattias <mattias@kojin.tech>
Subject: bug#71510: 30.0.50; kill-this-buffer must be bound to an event with parameters
Date: Wed, 12 Jun 2024 20:14:17 +0800 [thread overview]
Message-ID: <87le3a8ijq.fsf@yahoo.com> (raw)
In-Reply-To: <86bk461lf5.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 12 Jun 2024 13:54:06 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> tags 71510 notabug
> thanks
>
>> Date: Wed, 12 Jun 2024 11:06:36 +0200
>> From: Mattias <mattias@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.
Mattias, if it helps, such errors frequently indicate that the command
is being misapplied in contexts where `kill-current-buffer' is the
appropriate command.
next prev parent reply other threads:[~2024-06-12 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 9:06 bug#71510: 30.0.50; kill-this-buffer must be bound to an event with parameters Mattias
2024-06-12 10:54 ` Eli Zaretskii
2024-06-12 12:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-06-12 12:51 ` Mattias
2024-06-15 10:50 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87le3a8ijq.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=71510@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mattias@kojin.tech \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.