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

[Juri Linkov]

>> 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.
>
> Why removes? Each buffer should keep its "current error" state, and you'd
> switch between the navigations by switching to the errors-containing buffer
> (and calling some additional command), probably.

So do you propose to prefer buffer-local next-error-last-buffer
instead of window-local next-error-last-buffer?  This can cause
problems only when the same buffer can be visited from separate
next-error navigations, e.g. from two different *grep* buffers,
next-error from such buffer will use only the latest navigation
that visited this buffer (until it switched manually to another
navigation by a new command) Is this situation frequent enough?