-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Is it possible to cycle to prev instead of next? #599
Comments
Ow I guess I should have opened a blank issue as this is more a question then a feature request... Unless of course if it currently isn't possible 😉 |
Hey 👋 No, cycling in the opposite direction is currently not possible. |
Hmm... That might be a nice workflow for me as well. I'll give it a go... 👍🏻 |
BREAKING CHANGE: Running :rustLsp explainError will now only explain error on current line, users are suggested to use vim.diagnostic.goto_prev() and vim.diagnostic.goto_next() for navigation, as stated in issue mrcjkb#603 and mrcjkb#599
BREAKING CHANGE: Running :rustLsp explainError will now only explain error on current line, users are suggested to use vim.diagnostic.goto_prev() and vim.diagnostic.goto_next() for navigation, as stated in issue mrcjkb#603 and mrcjkb#599
BREAKING CHANGE: Running :rustLsp explainError will now only explain error on current line, users are suggested to use vim.diagnostic.goto_prev() and vim.diagnostic.goto_next() for navigation, as stated in issue mrcjkb#603 and mrcjkb#599
I have a custom function for moving around warnings and errors which I use for multiple languages. Plugging in
rustaceanvim
(after just finally moving away fromrust-tools
🙈) is super easy by adding an additionalelseif
like so:But I have two of these functions, one for moving to the next as shown above, but another one moving to the previous like this:
But in this case when in a Rust file it doesn't actually move to the previous. Is there a way to achieve this? Thanks!
The text was updated successfully, but these errors were encountered: