* File closed where edebug was running
@ 2025-01-05 13:18 Andreas Röhler
2025-01-05 15:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
0 siblings, 1 reply; 2+ messages in thread
From: Andreas Röhler @ 2025-01-05 13:18 UTC (permalink / raw)
To: help-gnu-emacs@gnu.org
Some function under edebug and closed that file by mistake, Emacs sends
an error in case that function is affected.
Depending on the function, that might make that instance of Emacs
unusable. Can't even save buffers any more.
Any suggestion?
Cheers,
Andreas
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: File closed where edebug was running
2025-01-05 13:18 File closed where edebug was running Andreas Röhler
@ 2025-01-05 15:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
0 siblings, 0 replies; 2+ messages in thread
From: Stefan Monnier via Users list for the GNU Emacs text editor @ 2025-01-05 15:11 UTC (permalink / raw)
To: help-gnu-emacs
> Some function under edebug and closed that file by mistake, Emacs sends an
> error in case that function is affected.
> Depending on the function, that might make that instance of Emacs
> unusable. Can't even save buffers any more.
Yup. Been there, done that.
> Any suggestion?
Add some defense-against-breakage in the relevant ELisp code.
Which code is "the relevant ELisp code" depends on the specifics, which
you have not provided.
Stefan
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-01-05 15:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-01-05 13:18 File closed where edebug was running Andreas Röhler
2025-01-05 15:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
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).