Re: next-error use cases

[Stephen Leake]

Dmitry Gutov <address@hidden> writes:

> On 4/8/18 11:26 PM, Clément Pit-Claudel wrote:
>
>> 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'm afraid that won't match the user's intention: if I just run Grep,
> I probably want to jump between its results, and not between Flyspell
> markers.

+1. I often have several compilation-mode buffers active (one from a
compile, one from a cross-reference tool, one from grep), and I expect
next-error to use the one I last chose.

I chose one by visiting the buffer, and using <ret> to go to an error.

So just be sure the user has a way to indicate which buffer/location
list is "current".

-- 
-- Stephe