all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mattias <mattias@kojin.tech>
Cc: 71510-done@debbugs.gnu.org
Subject: bug#71510: 30.0.50; kill-this-buffer must be bound to an event with parameters
Date: Sat, 15 Jun 2024 13:50:23 +0300	[thread overview]
Message-ID: <865xuav5sg.fsf@gnu.org> (raw)
In-Reply-To: <a251fe78-cd51-4125-a1f3-67be9999c5ff@kojin.tech> (message from Mattias on Wed, 12 Jun 2024 14:51:48 +0200)

> Date: Wed, 12 Jun 2024 14:51:48 +0200
> Cc: 71510@debbugs.gnu.org
> From: Mattias <mattias@kojin.tech>
> 
> 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`

I've now mentioned kill-current-buffer in the doc string, and I'm
therefore closing this bug.





      reply	other threads:[~2024-06-15 10:50 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
2024-06-12 12:51   ` Mattias
2024-06-15 10:50     ` Eli Zaretskii [this message]

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=865xuav5sg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71510-done@debbugs.gnu.org \
    --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.