Changing the behavior of display-buffer in next-error-no-select

Changing the behavior of display-buffer in next-error-no-select

[Richard Sent]

Hi Emacs,

When cycling through, say, a rgrep result buffer with n
(next-error-no-select) and p (previous-error-no-select), file results
are displayed in every open window, with the exception of the window
containing the rgrep results themselves.

I'd rather have file results remain in just one window so that I can use
other buffers while still viewing search results. Is this possible?

I see that next-error-no-select contains
display-buffer-overriding-action, so I suspect the answer might be
advising next-error-no-select and let-binding
display-buffer-overriding-action, but actually working that out is a bit
difficult.

How would I go about this? Are there any better options?

-- 
Take it easy,
Richard Sent
Making my computer weirder one commit at a time.

Re: Changing the behavior of display-buffer in next-error-no-select

[Juri Linkov]

> When cycling through, say, a rgrep result buffer with n
> (next-error-no-select) and p (previous-error-no-select), file results
> are displayed in every open window, with the exception of the window
> containing the rgrep results themselves.
>
> I'd rather have file results remain in just one window so that I can use
> other buffers while still viewing search results. Is this possible?
>
> I see that next-error-no-select contains
> display-buffer-overriding-action, so I suspect the answer might be
> advising next-error-no-select and let-binding
> display-buffer-overriding-action, but actually working that out is a bit
> difficult.
>
> How would I go about this? Are there any better options?

The problem is that the first thing that
'display-buffer-use-some-window' tries to do
is to find the least recently used window
with 'display-buffer--lru-window'.

I think this behavior should be customizable with a new option,
so that you could prefer always to use
the most recently used window.