unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: Undo defalias
Date: Fri, 03 Mar 2023 22:11:27 +0100	[thread overview]
Message-ID: <87r0u5czgg.fsf@telefonica.net> (raw)
In-Reply-To: jwvzg8thk9l.fsf-monnier+emacs@gnu.org

Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

>> The problem was caused by aggressive-indent-mode.el. It uses
>>
>> (cl-letf (((symbol-function 'message) #'ignore))
>>  ...
>
> So either:
> - you're still within the `cl-letf`.  In that case
>   `abort-recursive-edit` or some such should fix the problem.

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.

> - you're not within the `cl-letf` any more, in which case the question
>   becomes: how come `cl-letf` didn't restore the previous value?
>   `cl-letf` uses `unwind-protect` so it should restore the previous
>   binding reliably even in case of errors.
>
> [ 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.




  reply	other threads:[~2023-03-03 21:11 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 [this message]
2023-03-05  9:32         ` Madhu
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=87r0u5czgg.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --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).