Using 'next_result' is broken

We use ‘next_result’ as a recommendation to go to the next result (essentially F4 on Windows). As soon as you open a Find all which opens the ‘Find results’ view, this command will not work anymore. Instead it will correctly iterate the search results. But our panel never gains focus again. You can close the ‘Find results’ view, and still not iterate through the lint errors. You can ctrl-k a to open the errors panel, and still are not able to iterate through the lint errors. You have to literally click (activate) the panel, so Sublime will reactivate the shortcut/command ‘next_result’ for it.

• Either don’t use ‘next_result’ (this would help #1010 as well) at all, and instead recommend the Goto command. (We could implement going to the next file for that command as well.)
• Actually focus the panel on ‘ctrl-k a’

[braver]

It’s just a built-in feature. Although I don’t think many people will know about, I don’t really feel like telling people about it and then having to discuss its shortcomings. If people do know about it and find out it works here too, they can consider it some little extra nugget of functionality they got for free. It’s not like ST documents what “next_result” means in any way.

[FichteFoll]

Hm, imo it’s still worth mentioning that it is supported, albeit it can bug out in some situations as outlined in OP, which I think of as ST bugs. It could, however, occur that indicating support for them would cause people to blame SL for next_result problems when it’s in fact just re-using ST behavior.