unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	npostavs@gmail.com, bugs@gnu.support, 37352@debbugs.gnu.org
Subject: bug#37352: 27.0.50; recursive-edit aborts on elisp error after evaluation
Date: Mon, 23 Sep 2019 12:18:26 +0200	[thread overview]
Message-ID: <87k19zb9jh.fsf@gnus.org> (raw)
In-Reply-To: <83o8zcp4zd.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 22 Sep 2019 21:20:54 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Like C-M-c?
>
> Yes, like C-M-c.

Hm; I never considered that `C-M-c' would be a good way to exit the
debugger -- perhaps this should be mentioned in the doc string?

Or perhaps we could bind, say, `Q', to `exit-recursive-edit' in that
mode?

I just had a look at the doc string -- I'm not quite sure what the
second paragraph tries to say, but it seems to be grammatically dubious,
anyway.  Perhaps somebody who knows what this means can fix that
sentence up, anyway?  :-)

---
A line starts with ‘*’ if exiting that frame will call the debugger.
Type b or u to set or remove the ‘*’.

When in debugger due to frame being exited,
use the r command to override the value
being returned from that frame.

Use M-x debug-on-entry and M-x cancel-debug-on-entry to control
which functions will enter the debugger when called.


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-09-23 10:18 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
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 [this message]
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=87k19zb9jh.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=37352@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    --cc=eliz@gnu.org \
    --cc=npostavs@gmail.com \
    --cc=schwab@linux-m68k.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).