On 23/05/2020 21.36, Dmitry Gutov wrote:
For error navigation, it /could/ be a better idea, but IMHO it's like we'd be giving up and creating a parallel set of
variables and commands for "local" errors. And necessitate a "muscle memory" context switch when
one goes from "local" errors to "global" or back. One set of bindings would also have to be more
awkward than the other.
Good points all around, and I don't have much more to contribute :)
There's also another wrinkle: I think there was a proposed feature for Flycheck
to list errors for multiple files (or the whole project) together? 'next-error'
could be handy for jumping between those too.
We do this currently already, and the idea is that all external errors are
converted into local errors on line 1.
In the error list they appear with a file name and a line number in that file,
so if you were to cycle errors relative to that list you would visit files one
by one, and if you were to visit errors relative to the buffer you'd go through
all local errors then jump to another file with errors, if any.