GNU bug report logs - #32825
27.0.50; Deterministic window management

Previous Next

Full log

View this message in rfc822 format

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 32825 <at> debbugs.gnu.org, Noam Postavsky <npostavs <at> gmail.com>, Juri Linkov <juri <at> linkov.net>
Subject: bug#32825: 27.0.50; Deterministic window management
Date: Mon, 01 Oct 2018 20:10:39 +0200

martin rudalics <rudalics <at> gmx.at> writes:

> > What I don't like so much is that, in effect, we use
> > `display-buffer-in-previous-window', whose behavior is user
> > configurable, but we don't like some if its semantics, so we overwrite
> > them by specifying the previous-window property dynamically generated.
> > This does what we want, but it is not user configurable any more.  If,
> > for example, a user wants to always use a special frame for the
> > debugger, he can't get that.
>
> Why not?  Users can always provide their customizations via
> 'display-buffer-alist'.  Using, for example
>
> (push '("*Backtrace*" (display-buffer-reuse-window
> display-buffer-pop-up-frame) (reusable-frames . t))
>       display-buffer-alist)

What I meant was "always use a special, but always one and the same
frame".  The 'reusable-frame' association in your 'display-buffer-alist'
entry doesn't accomplish that, because when pop-to-buffer is called, the
*Backtrace* buffer is typically not shown anymore at that moment in that
frame.


Michael.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.