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

From: Dmitry Gutov <[email-masked]>
Date: Mon, 22 Feb 2016 19:30:21 +0200

On 02/22/2016 07:22 PM, Eli Zaretskii wrote:

> Will do.  To make this more efficient, can you suggest what situations
> to try?

That's what I'm really asking: which scenario did you find most broken 
before, and does it work better now?