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

Previous Next

Full log

View this message in rfc822 format

From: martin rudalics <rudalics <at> gmx.at>
To: Juri Linkov <juri <at> linkov.net>
Cc: Michael Heerdegen <michael_heerdegen <at> web.de>, 32825 <at> debbugs.gnu.org
Subject: bug#32825: 27.0.50; Deterministic window management
Date: Sun, 30 Sep 2018 10:00:10 +0200

>>> Another problem with 'append' is that when the user switches
>>> to the window where *Backtrace* was displayed last time,
>>> and types 'C-x C-e' in that window, then *Backtrace* will be
>>> displayed in the same window.  Maybe it should have
>>> (inhibit-same-window . t)?
>>
>> I wouldn't mind adding such a restriction.  Would you condition it on
>> the 'append' case or do it generally?
>
> It seems this problem doesn't exist for other cases.

But could it harm to add an 'inhibit-same-window' for other cases?

Anyway, could you provide a patch?  To be honest, I don't grok the
idea of 'debugger-previous-window' in

	      (pop-to-buffer
	       debugger-buffer
	       `((display-buffer-reuse-window
		  display-buffer-in-previous-window)
		 . (,(when (and (window-live-p debugger-previous-window)
				(frame-visible-p
				 (window-frame debugger-previous-window)))
		       `(previous-window . ,debugger-previous-window)))))

any more and am afraid to do more damage than fix anything.

martin

Previous Next

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