Re: [PATCH] Fix display-buffer-use-some-window to honor reusable-frames

[Eli Zaretskii <eliz@gnu.org>]

> Date: Fri, 3 Feb 2023 10:09:02 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org, larsi@gnus.org
> From: martin rudalics <rudalics@gmx.at>
> 
>  > This patch produces the desired behavior for me and matches
>  > the xemacs behavior when I use the following.
>  >
>  > (setq display-buffer-base-action '((display-buffer-use-least-recent-window)
>  > (not-this-window . t)))
>  >
>  > The explicit not-this-window is required to get display-buffer-pop-up-window
>  > to trigger in a single window single frame case. It might be worth adding a
>  > note
>  > to that effect to the docstring?
> 
> Silly me.  Please try again with the attached.  Then
> 
> (setq display-buffer-base-action '((display-buffer-use-least-recent-window)))
> (display-buffer "*Messages*")
> 
> should work as expected.
> 
>  > This results in the behavior of the example matching that of xemacs.
>  > With the lru-time option enabled the display multiple buffers case seems
>  > to be served (I assume there is some other mechanism that can be used
>  > to restore the previous window configuration in such cases that is not
>  > included in this example).
> 
> Sorry.  I don't grok what you said in parentheses here.
> 
> martin
> 
> diff --git a/lisp/window.el b/lisp/window.el
> index a11293d372..dffcc14ac3 100644
> --- a/lisp/window.el
> +++ b/lisp/window.el

Tom, would you please respond to Martin's latest message (quoted
above)?  I'd like to wrap up the investigation of this issue and
install whatever changes you two agree upon, so that we could proceed
with producing the first pretest of Emacs 29.1.

TIA