bug#45688: 28.0.50; New action for display-buffer?

[martin rudalics]

>> This
>>
>> +  (when-let ((window (display-buffer-use-some-window
>> +                      buffer (cons (cons 'inhibit-same-window t) alist))))
>> +    (window-bump-use-time window)))
>>
>> alone will bump the use time for a _reused_ window only.  A freshly
>> popped up window will continue to be the first candidate for reuse and
>> only then enter the cycle of windows to reuse.
>
> How do we bump the use to for a new window, then?

By bumping the time stamp of _any_ window 'display-buffer' uses for
displaying a buffer (just like XEmacs does).

>> XEmacs treats _all_ windows it creates or uses equal in this regard
>> including those on other frames.
>
> Oh, other frames, too...  I think we'll leave that as an exercise for
> the reader.

Then when you switch from one frame to another, any problems you've
found on the previous frame will immediately reemerge on the new frame.

>>> The only oddity is that it'll resize windows to their previous sizes --
>>> is there any way to inhibit that?
>>
>> How comes that window gets ever resized in the first place?
>
> I have no idea, but it's totally repeatable -- the window that's
> switched to becomes the largest window, and it's rather distracting.

Please put some silly function on 'window-size-change-functions' and
make it produce a backtrace.

martin