|
From: | martin rudalics |
Subject: | bug#45688: 28.0.50; New action for display-buffer? |
Date: | Thu, 7 Jan 2021 17:54:39 +0100 |
> But with this setting: > > (setq display-buffer-base-action '(display-buffer-use-least-recent-window)) > > it's quite XEmacs-like? But this should be expressed in terms of `display-buffer-alist'. > I think? At least in my tests. So now we've > got that all-important ex-XEmacs market segment covered. 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. XEmacs treats _all_ windows it creates or uses equal in this regard including those on other frames. > 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? martin
[Prev in Thread] | Current Thread | [Next in Thread] |