Hi,
I found this plugin very useful, but it has one limitation. How can user jump between errors/warnings (basically between signs)? If file is long it would be convenient to have such functionality and I wonder if it can be implemented.
Thanks,
Valentin
syntastic uses vims built in location lists to store errors. So if a buffer has errors, you can use :lnext and :lprev. See :help :lnext for info.
You may also want to consider installing unimpared from here https://github.com/tpope/vim-unimpaired which adds some easy mappings for jumping around the location list i.e. [l and ]l (along with lots of other similarly themed mappings) - or you could just add the mappings yourself if you dont want another plugin :)
Very nice, I'll appreciate if you'll add this to documentation.
Ill add this to the FAQ section
By default, :lnext, :lprev etc. results in a red "E42: No Errors". In order to get :lnext, etc. to work (manually), I had to run :Errors (followed by :lclose to hide the location window).
If you want to automatically enable the feature, use let g:syntastic_always_populate_loc_list = 1, as mentioned in the documentation.
@Rob--W: Well, :lnext and :lprev are standard Vim commands, and they work only with loclists. Syntastic doesn't update the loclists unless you tell it to do so, mainly in order not to interfere with the various grep-like plugins people might use. So yes, you need to set g:syntastic_always_populate_loc_list to be able to use :lnext and :lprev, and no, there is no other mechanism to jump between errors that doesn't use loclists.
Funny, but it doesn't work for me. It says "No Errors".
I have let g:syntastic_always_populate_loc_list = 1 in my .vimrc.
@daGrevis Please upgrade to master HEAD and try again. If it still see the problem you're accusing, please open a new report and explain what you did, what you expected to happen, and what happened instead.
Well it works fine now. :dancer:
Even with g:syntastic_always_populate_loc_list = 1, the location list isn't populated until calling Errors.
@fweep Please open a __new__ issue. Explain what you did, what did you expected to happen, and what happened instead.
This only works for errors, what about warnings?
@brandonsturgeon Congratulations: you won the "Thread necromancer of the year" award.
Most helpful comment
By default,
:lnext,:lprevetc. results in a red "E42: No Errors". In order to get:lnext, etc. to work (manually), I had to run:Errors(followed by:lcloseto hide the location window).If you want to automatically enable the feature, use
let g:syntastic_always_populate_loc_list = 1, as mentioned in the documentation.