bug#70949: display-buffer-choose-some-window

[Juri Linkov]

> Consider these minor changes for the Elisp manual
>
> The above describes the behavior when the @code{some-window} @var{alist}
> entry is @code{lru} or @code{nil} which is the default.  Another
> possible value is @code{mru}.  If, for example,
> @code{display-buffer-base-action} is customized to @w{@code{(nil
> . ((some-window . mru)))}}, then this function will prefer the most
> recently used window.  This will try to display several buffers from
> consecutive calls of @code{display-buffer} in the same window.  Consider
> a configuration of three or more windows where a user wants to consult,
> in a non-selected window, one after the other, the results of a query
> spread among several buffers.  With the @code{lru} strategy, Emacs may
> continuously choose another window because the least recently used
> window changes with every call of @code{display-buffer-use-some-window}.
> With the @code{mru} strategy, the window chosen would always remain the
> same, resulting in a predictable user experience.
>
> and this for the NEWS entry:
>
> *** New action alist entry 'some-window' for 'display-buffer'.
> It specifies which window 'display-buffer-use-some-window' should prefer.
> For example, when 'display-buffer-base-action' is customized to
> '(nil . ((some-window . mru)))', then a buffer will be displayed
> in the same most recently used window from consecutive calls of
> 'display-buffer' (in a configuration with more than two windows).

Thanks, now pushed.