GNU bug report logs -
#32825
27.0.50; Deterministic window management
Previous Next
Reported by: Juri Linkov <juri <at> linkov.net>
Date: Mon, 24 Sep 2018 19:15:02 UTC
Severity: minor
Tags: moreinfo
Found in version 27.0.50
Fixed in version 29.0.50
Done: Juri Linkov <juri <at> linkov.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
martin rudalics <rudalics <at> gmx.at> writes:
> > This provides a nicer behavior because display-buffer-at-bottom tries
> > to resize other windows to accommodate the *Backtrace*.
>
> I think we should first investigate the 'debugger-previous-window'
> resettings. Maybe Michael can help.
I'm not sure how I can be of help.
There are only two places where debugger-previous-window is set - both
in `debug': in the first, the value is set when the debugger pops up, to
the window that has been chosen to display it. In the second place,
it's reset to nil when the debugger "won't be back".
So, when the value is a (live) window, it should be respected. I didn't
follow your discussion very attentively, but I'm not sure how the
debugger-previous-window variable is concerned in what you discussed
recently. AFAIK its only use is to remember the window while a debugger
session is still active.
Michael.
This bug report was last modified 3 years and 24 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.