From: Noam Postavsky <npostavs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, Jean Louis <bugs@gnu.support>,
37352@debbugs.gnu.org
Subject: bug#37352: 27.0.50; recursive-edit aborts on elisp error after evaluation
Date: Sun, 22 Sep 2019 12:39:31 -0400 [thread overview]
Message-ID: <871rw89tfg.fsf@gmail.com> (raw)
In-Reply-To: <e29ffec8-666d-4174-9a08-f20343d9b176@default> (Drew Adams's message of "Sun, 22 Sep 2019 09:14:21 -0700 (PDT)")
On Sun, 22 Sep 2019 at 12:15, Drew Adams <drew.adams@oracle.com> wrote:
>
> > I don't know why the `q' command in the debugging mode
> > is defined that way.
>
> Uh, because it makes sense? The recursive edit
> was entered only for use of the debugger.
There are two recursive edits, one that the OP entered from their code
(I assume for the edit-file-and-return-as-string stuff [1]), and a
second nested one that happend after an error was signaled and the
debugger was invoked. Then quitting the debugger exits both recursive
edits, because q is bound to top-level in debugger-mode, and top-level
aborts all recursive edits, not just the latest one.
A possible solution might be to bind q to a command which quits
recursive edits only up to the one that the debugger invoked.
[1]: https://lists.gnu.org/archive/html/help-gnu-emacs/2019-08/msg00051.html
next prev parent reply other threads:[~2019-09-22 16:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 7:41 bug#37352: 27.0.50; recursive-edit aborts on elisp error after evaluation Jean Louis
2019-09-20 18:30 ` Lars Ingebrigtsen
2019-09-20 19:09 ` Jean Louis
2019-09-20 21:01 ` Lars Ingebrigtsen
2019-09-22 12:57 ` Jean Louis
2019-09-22 13:00 ` Lars Ingebrigtsen
2019-09-22 13:04 ` Jean Louis
2019-09-22 13:49 ` Lars Ingebrigtsen
2019-09-22 16:14 ` Drew Adams
2019-09-22 16:39 ` Noam Postavsky [this message]
2019-09-22 16:55 ` Drew Adams
2019-09-22 16:59 ` Eli Zaretskii
2019-09-22 17:54 ` Andreas Schwab
2019-09-22 18:20 ` Eli Zaretskii
2019-09-23 10:18 ` Lars Ingebrigtsen
2019-09-23 12:43 ` Noam Postavsky
2019-09-23 14:01 ` Lars Ingebrigtsen
2019-09-23 14:14 ` Andreas Schwab
2019-09-25 8:11 ` Eli Zaretskii
2019-09-25 13:09 ` Lars Ingebrigtsen
2019-09-22 16:58 ` Eli Zaretskii
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=871rw89tfg.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=37352@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).