From: Madhu <enometh@meer.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Undo defalias
Date: Sun, 05 Mar 2023 15:02:47 +0530 [thread overview]
Message-ID: <m3edq3bl1c.fsf@leonis4.robolove.meer.net> (raw)
In-Reply-To: 87r0u5czgg.fsf@telefonica.net
* Óscar Fuentes <87r0u5czgg.fsf @telefonica.net> :
Wrote on Fri, 03 Mar 2023 22:11:27 +0100:
> I don't have the problematic session around anymore, but I recall seeing
> a *Backtrace* buffer among the list of existing buffers. However, IIRC
> Emacs says that a recursive edit is active and that indication was not
> there.
>> [ There's admittedly the possibility/risk that you hit `C-g` (or some
>> similar error occurred) right at the specific moment when `cl-letf`
>> was executing the second part of the `unwind-protect` (i.e. the one
>> that reset `message` to its previous definition).
>> That's a known hole in our system. ]
>
> That's also quite plausible, indeed. I tend to use C-g quite frequently.
Many a time in emacs-29.50.x I've got into the situation where I haven't
been able to return from a recursive-edit. i.e. (minibuffer-depth) is
never 0, and with minibuffer-depth-indicate-mode I'd always see a [2] in
the minibuffer. Admittedly this has happened less often recently.
Perhaps I was hitting this code path?
next prev parent reply other threads:[~2023-03-05 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 1:23 Undo defalias Óscar Fuentes
2023-02-28 9:17 ` Gregory Heytings
2023-02-28 15:56 ` Óscar Fuentes
2023-03-01 20:36 ` Emanuel Berg
2023-03-03 15:29 ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-03-03 15:37 ` Gregory Heytings
2023-03-03 15:49 ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-03-03 15:52 ` Eli Zaretskii
2023-03-03 16:01 ` Gregory Heytings
2023-03-03 16:00 ` Óscar Fuentes
2023-03-03 16:17 ` Gregory Heytings
2023-03-03 16:33 ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-03-03 21:11 ` Óscar Fuentes
2023-03-05 9:32 ` Madhu [this message]
2023-03-03 22:58 ` Gregory Heytings
2023-03-04 0:05 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3edq3bl1c.fsf@leonis4.robolove.meer.net \
--to=enometh@meer.net \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).