unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* location of "*Backtrace*" buffer
@ 2014-06-22 13:16 Toomas Rosin
  2014-06-24  1:39 ` Michael Heerdegen
  0 siblings, 1 reply; 3+ messages in thread
From: Toomas Rosin @ 2014-06-22 13:16 UTC (permalink / raw)
  To: help-gnu-emacs

Hello!

I have an Emacs session running for about three weeks now.  A couple of days ago, a strange phenomenon started to occur: each time I do something which invokes the debugger (e.g., do a `yank-pop' without a preceding `yank'), the backtrace buffer appears always in one and the same frame (instead of in the frame from which I issued the offending command), which is especially annoying when I happen to work in another frame, on another desktop (which in fact means almost always).  (I'm working under KDE.)  What could be the matter?  Is there a way to get the normal behaviour back without exiting Emacs and without closing the frame in which the backtrace buffer now always appears?

I have `display-buffer-reuse-frames' set to `t', but resetting it to `nil' has no effect in this respect.  I also tried playing with `debugger-bury-or-kill' (from debug.el), with no luck.

Can somebody help me?

Thanks in advance,
T.




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: location of "*Backtrace*" buffer
  2014-06-22 13:16 location of "*Backtrace*" buffer Toomas Rosin
@ 2014-06-24  1:39 ` Michael Heerdegen
  0 siblings, 0 replies; 3+ messages in thread
From: Michael Heerdegen @ 2014-06-24  1:39 UTC (permalink / raw)
  To: help-gnu-emacs

Toomas Rosin <toomas@rosin.ee> writes:

> I have an Emacs session running for about three weeks now.  A couple
> of days ago, a strange phenomenon started to occur: each time I do
> something which invokes the debugger (e.g., do a `yank-pop' without a
> preceding `yank'), the backtrace buffer appears always in one and the
> same frame (instead of in the frame from which I issued the offending
> command), which is especially annoying when I happen to work in
> another frame, on another desktop (which in fact means almost always).
> (I'm working under KDE.)  What could be the matter?

AFAICT, this behavior is in general not unintended.  In prior Emacs
versions, there was a problem that when you hit e.g. d d ... in the
debugger, the backtrace buffer sometimes was displayed in another window
for every time you hit d.

What you see is probably an annoying consequence of the related fix.
I suggest to make a bug report.

> Is there a way to
> get the normal behaviour back without exiting Emacs and without
> closing the frame in which the backtrace buffer now always appears?

Try evaluating (setq debugger-previous-window nil).


Michael.




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: location of "*Backtrace*" buffer
@ 2014-06-29 18:01 Toomas Rosin
  0 siblings, 0 replies; 3+ messages in thread
From: Toomas Rosin @ 2014-06-29 18:01 UTC (permalink / raw)
  To: michael_heerdegen, help-gnu-emacs

> Try evaluating (setq debugger-previous-window nil).

It worked!  Thank you very much!

T.




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-06-29 18:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-22 13:16 location of "*Backtrace*" buffer Toomas Rosin
2014-06-24  1:39 ` Michael Heerdegen
  -- strict thread matches above, loose matches on Subject: below --
2014-06-29 18:01 Toomas Rosin

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).