From: Michael Heerdegen <michael_heerdegen@web.de>
To: Toomas Rosin <toomas@rosin.ee>
Cc: 17882@debbugs.gnu.org
Subject: bug#17882: 24.3; *Backtrace* buffer appearing in the wrong frame
Date: Mon, 30 Jun 2014 18:00:26 +0200 [thread overview]
Message-ID: <871tu64cbp.fsf@web.de> (raw)
In-Reply-To: <10176744.CSMpqoKfbG@toomas> (Toomas Rosin's message of "Mon, 30 Jun 2014 13:11:20 +0300")
Toomas Rosin <toomas@rosin.ee> writes:
> > What you see is probably an annoying consequence of the related fix.
> > I suggest to make a bug report.
Thanks, Toomas.
I think the debugger is now too strict about reusing the last used
window. `debug` prefers the remembered `debugger-previous-window`.
AFAIK, this variable is never unset, so the debugger tries to reuse the
last used window even when the last debugging session was over for
hours. This is a problem when that window is still existing, but not
"reachable" (say, on another display).
This is the relevant code in `debug`:
(pop-to-buffer
debugger-buffer
`((display-buffer-reuse-window
display-buffer-in-previous-window)
. (,(when debugger-previous-window
`(previous-window . ,debugger-previous-window)))))
Should we add a test whether `debugger-previous-window`s frame fulfills
(lambda (frame) (eq t (frame-visible-p frame))) ?
Thanks,
Michael.
next prev parent reply other threads:[~2014-06-30 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 10:11 bug#17882: 24.3; *Backtrace* buffer appearing in the wrong frame Toomas Rosin
2014-06-30 16:00 ` Michael Heerdegen [this message]
2017-10-13 3:02 ` Noam Postavsky
2017-10-13 10:10 ` Michael Heerdegen
2017-10-15 18:24 ` Noam Postavsky
2017-10-14 8:35 ` martin rudalics
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=871tu64cbp.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=17882@debbugs.gnu.org \
--cc=toomas@rosin.ee \
/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.