unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: dick <dick.r.chiang@gmail.com>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 55863@debbugs.gnu.org
Subject: bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace*
Date: Fri, 10 Jun 2022 11:27:15 +0200	[thread overview]
Message-ID: <875yl8x40c.fsf@gnus.org> (raw)
In-Reply-To: <878rq54omf.fsf@dick> (dick's message of "Thu, 09 Jun 2022 15:34:48 -0400")

dick <dick.r.chiang@gmail.com> writes:

>> FWIW I agree with this: I'm often annoyed that the backtrace is
>> removed.  What's the harm in leaving it there?
>
> Because inhibit-debugger silently won't let you have more than one
> active session.  This was as confusing to me as a edebug beginner as
> when gdb inexplicably flies past a breakpoint.

Removing the text from the *Backtrace* buffer (or not) doesn't affect
whether `inhibit-debugger' is bound or not.  The `q' from the buffer
exits the recursive edit, which makes `inhibit-debugger' go back to its
normal value.

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





  parent reply	other threads:[~2022-06-10  9:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 21:28 bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace* dick.r.chiang
2022-06-09  5:45 ` Eli Zaretskii
2022-06-09  6:46 ` Juri Linkov
2022-06-09 10:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-09 12:59 ` Lars Ingebrigtsen
2022-06-09 13:51   ` dick
2022-06-09 16:01     ` Lars Ingebrigtsen
2022-06-09 16:58     ` Juri Linkov
2022-06-09 17:34       ` Lars Ingebrigtsen
2022-06-09 17:58         ` Juri Linkov
2022-06-09 18:44           ` Lars Ingebrigtsen
2022-06-09 18:50         ` Drew Adams
2022-06-09 18:57         ` Eli Zaretskii
2022-06-09 19:02           ` Lars Ingebrigtsen
2022-06-09 18:56       ` Eli Zaretskii
2022-06-09 19:17       ` Eric Abrahamsen
2022-06-09 19:34         ` dick
2022-06-09 21:02           ` Eric Abrahamsen
2022-06-10  9:27           ` Lars Ingebrigtsen [this message]
2022-06-10 10:03             ` dick
2022-06-10 10:06               ` Lars Ingebrigtsen
2022-06-10 10:24                 ` dick
2022-06-10 11:39                   ` dick
2022-06-14 12:39                     ` Lars Ingebrigtsen

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=875yl8x40c.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=55863@debbugs.gnu.org \
    --cc=dick.r.chiang@gmail.com \
    --cc=eric@ericabrahamsen.net \
    /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).