bug#28864: 25.3.50; next-error-no-select does select

[Juri Linkov <juri@linkov.net>]

> My scenario template is basically this:
>
> 1. Visit a buffer <A> in some major mode, press M-x next-error or M-x
> previous-error an arbitrary number of times, visiting the appropriate error
> locations, whether they are in the current buffer or in some other buffers
> or files that will have to be opened.
>
> 2. The above should happen fine irrespective of the current window
> configuration, and whether the buffer <A> gets hidden for some reason
> during this process (and we do know the possible reasons).

It's a step backward: it removes the ability to run several next-error
navigations simultaneously.  Currently it's possible to visit e.g.
compilation results in one frame, and e.g. grep hits in another frame
at the same time without affecting one another.  Undoubtedly, relying
on the frame confines or on the buffer visibility is far from ideal.

One solution that I proposed was to associate a window containing
a navigated buffer with its next-error capable buffer, so that
next-error issued in the same window will continue visiting other matches
from the same next-error buffer (regardless whether it's hidden or not).
This assumes there will be a command to disassociate a window
from its next-error buffer, and switch to another next-error buffer.

Do you have a better idea?