Subject: bug#20489: 25.0.50; next-error-find-buffer chooses non-current buffer without good reason

From: Dmitry Gutov <[email-masked]>
Date: Tue, 1 Mar 2016 01:30:37 +0200

On 02/29/2016 06:23 PM, Eli Zaretskii wrote:

> Really?  Isn't that strange?  Doesn't every user of next-error want
> that?

Just yet another way next-error-function is broken, it seems.

> Please uncomment those lines, if you didn't already.

Already did, in aae436e2d898a8c8cc243c73d6cec5a8c566a061.