GNU bug report logs -
#71510
30.0.50; kill-this-buffer must be bound to an event with parameters
Previous Next
Reported by: Mattias <mattias <at> kojin.tech>
Date: Wed, 12 Jun 2024 10:37:03 UTC
Severity: normal
Tags: notabug
Found in version 30.0.50
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #21 received at 71510-done <at> debbugs.gnu.org (full text, mbox):
> Date: Wed, 12 Jun 2024 14:51:48 +0200
> Cc: 71510 <at> debbugs.gnu.org
> From: Mattias <mattias <at> 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.
This bug report was last modified 1 year and 12 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.