add support for rust-analyzer.runSingle for cargo #362
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you. Please fix some reviewdoc fixes. |
|
Fixed lint issues |
|
Thank you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Demo: https://asciinema.org/a/381194
This is how it shows in vim:
This is how vscode works:
In the future we might want vim-lsp to support virtual text for codelens so it is easier to discover like in vscode. Currently it is a bit difficult to see.
Added a util method so we can easily spawn terminal in both vim and neovim.
lsp_settings#utils#term_start.This would be really useful to run tests or snippet of code. This could ideally help remove plugins such as vim-test