From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 36067@debbugs.gnu.org
Subject: bug#36067: 27.0.50; Edebug leaves undefined RET in minibuffer
Date: Sun, 21 Apr 2024 08:02:33 +0200 [thread overview]
Message-ID: <87o7a3i77q.fsf@web.de> (raw)
In-Reply-To: <87sezfibr9.fsf@web.de> (Michael Heerdegen via's message of "Sun, 21 Apr 2024 06:24:26 +0200")
I had written:
> #+begin_src emacs-lisp
> (defvar a 0)
>
> (unwind-protect
> (progn (setq a 27)
> (message "%d" (+ a 19)))
> (setq a 0))
> #+end_src
>
> When you edebug the `unwind-protect' form and hit q (quit) when the
> `message' call has been reached, your session will remain with a binding
> of 27 for a - which is normally impossible and should never happen.
Although - I apologize - this is not what is happening: Edebug always
stops at the unwind forms.
I guess what I always do is thinking: "I said quit, why does it stop
again?" and quit again - which then explicitly skips the execution of
any unwind forms - bad for me.
So: should quitting maybe also set the mode to something like Go-nonstop
before calling `top-level' - would that behave better?
Michael.
prev parent reply other threads:[~2024-04-21 6:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 2:20 bug#36067: 27.0.50; Edebug leaves undefined RET in minibuffer Michael Heerdegen
2019-06-21 10:14 ` Noam Postavsky
2019-06-21 14:59 ` Michael Heerdegen
2019-07-09 2:08 ` Michael Heerdegen
2019-06-21 15:14 ` Eric Abrahamsen
2019-06-21 15:59 ` Michael Heerdegen
2019-06-22 8:22 ` martin rudalics
2021-08-10 16:11 ` Lars Ingebrigtsen
2024-04-21 4:24 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-21 6:02 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors [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=87o7a3i77q.fsf@web.de \
--to=bug-gnu-emacs@gnu.org \
--cc=36067@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.