Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to jump to single error #249

Closed
landersson opened this issue Sep 20, 2018 · 3 comments
Closed

Unable to jump to single error #249

landersson opened this issue Sep 20, 2018 · 3 comments

Comments

@landersson
Copy link

Apologies if this has been asked before or is not at all related to vim-dispatch.

I'm trying to use vim-dispatch with cargo (rust). My issue is that if there is only a single error, the cursor wont automatically jump to the location of the error in the source file, and using vim-unimpaired's [q or ]q (:cnext, :cprev) will just give me the error "No more items". I can still jump to the first(only) error by switching focus to the quickfix window and pressing enter, or running :cc 1, but that's a bit inconvenient. If there are multiple errors, using :cnext or :cprev works fine.

Is there a way to have ":Make" automatically jump to the first and single error, or at least make it possible to jump to a single error using [q or ]q?

@landersson
Copy link
Author

I just realised that I can mostly work around this by using [Q, i.e :cfirst.

If would still be nice to have :Make automatically jump to the first error on synchronous builds though.

@tpope
Copy link
Owner

tpope commented Sep 20, 2018

Your use of "synchronous" is confusing here, it's only synchronous if you're using an unsupported setup. If that's what you're doing, you may as well use :make.

@landersson
Copy link
Author

Ok, that makes sense. I was probably a bit mistaken about the main purpose of vim-dispatch. The problem that I originally wanted to solve was getting coloured error messages in quickfix, but I've realized vim-dispatch, even with a :terminal as an adapter, wont help me with that. Still a very useful plugin though. I'll close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants