Re: next-error use cases

[Eli Zaretskii]

> From: Clément Pit-Claudel <address@hidden>
> Date: Sun, 8 Apr 2018 16:26:59 -0400
> 
> > We could try to define priorities by ‘add-function’.
> 
> Or we could query all backends and go to the closest location.  It would 
> match with what the user sees on the screen: if I have a flyspell underline 
> followed by a FlyCheck error, it would visit one then the other.

I don't think "closest location" is a reliable indicator in this
case.  next-error exists to go to the next/previous locus, which could
be far away.