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

[Dmitry Gutov]

On 10/28/17 11:54 PM, Juri Linkov wrote:

> Please don't remove next-error-last-buffer from change-log-mode.
> Actually it is legitimate use according to the documentation
> of next-error-last-buffer:
> "The most recent ‘next-error’ buffer.
>   A buffer becomes most recent when its compilation, grep, or
>   similar mode is started, or when it is used with \\[next-error]."

The fact that it's documented doesn't exactly mean that the behavior 
really makes sense or is optimal.

> The problem occurred because two next-error buffer windows (*grep* and
> next-error capable ChangeLog) were both visible on the selected frame,
> but I believe we could fix this in the inner logic of next-error.

We've discussed the visibility-based selection before, I still don't 
think it makes sense, and the present bug report is evidence.