all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Juri Linkov <juri@linkov.net>
Cc: "55863@debbugs.gnu.org" <55863@debbugs.gnu.org>,
	dick <dick.r.chiang@gmail.com>
Subject: bug#55863: 29.0.50; [PATCH] Avoid hanging chad of *Backtrace*
Date: Thu, 9 Jun 2022 18:50:34 +0000	[thread overview]
Message-ID: <SJ0PR10MB54884AAC60F2260BF5DED938F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <878rq5zqod.fsf@gnus.org>

(Apologies for not following this thread.
Please ignore if not relevant.)

I'm just wondering whether option
`debugger-bury-or-kill' might be relevant here.

The default value is `bury'.  I'm guessing
maybe setting the value to `kill' would help
with what's being requested.

------------8<----------------
debugger-bury-or-kill is a variable defined in `debug.el'.

Its value is 'bury'

Documentation:
What to do with the debugger buffer when exiting `debug'.
The value affects the behavior of operations on any window
previously showing the debugger buffer.

nil means that if its window is not deleted when exiting the
  debugger, invoking `switch-to-prev-buffer' will usually show
  the debugger buffer again.

`append' means that if the window is not deleted, the debugger
  buffer moves to the end of the window's previous buffers so
  it's less likely that a future invocation of
  `switch-to-prev-buffer' will switch to it.  Also, it moves the
  buffer to the end of the frame's buffer list.

`bury' means that if the window is not deleted, its buffer is
  removed from the window's list of previous buffers.  Also, it
  moves the buffer to the end of the frame's buffer list.  This
  value provides the most reliable remedy to not have
  `switch-to-prev-buffer' switch to the debugger buffer again
  without killing the buffer.

`kill' means to kill the debugger buffer.

The value used here is passed to `quit-restore-window'.

You can customize this variable.

This variable was introduced, or its default value was changed, in
version 24.3 of Emacs.
------------8<----------------





  parent reply	other threads:[~2022-06-09 18:50 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB54884AAC60F2260BF5DED938F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=55863@debbugs.gnu.org \
    --cc=dick.r.chiang@gmail.com \
    --cc=juri@linkov.net \
    --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 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.