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

[Dmitry Gutov]

On 10/24/17 11:22 PM, Juri Linkov wrote:

> So do you propose to prefer buffer-local next-error-last-buffer
> instead of window-local next-error-last-buffer?

Maybe something like this:

- Make next-error-last-buffer always buffer-local.

- Create the "current next-error source buffer" variable (which we'll 
need anyway), and whenever we need to look up or set 
next-error-last-buffer, read it or set it in that 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?

Hopefully the above resolves your concern. But yes, switching to another 
navigation will require calling a certain new command.