3 ms·

Is it possible to get the inline inferred type annotations to show up in Vim the way they do in VSCode? I have been making a strong push to move to 100% Vim fo

Is it possible to get the inline inferred type annotations to show up in Vim the way they do in VSCode? I have been making a strong push to move to 100% Vim for development, but those inline annotations in VSCode with rust analyzer are amazing, especially while I'm still learning Rust. I'm currently using YouCompleteMe with rust-analyzer, plus rust-vim for autoformatting

ibraheemdev 6y ago
I use coc.nvim with rust-analyzer and I find it amazing. I used a more lightweight lsp client in the past, but I find the more full-featured coc.nvim to be the best balance - I get all the benefits of an IDE + the productivity of vim. coc is based on the VSCode intelli-sense engine and enables inline type-annotations by default, but I am not sure if "regular" vim (not neovim) supports it.
- ruph123 6y ago
  Can you please share your config? I find configuring coc quite painful.
  - ibraheemdev 6y ago
    I actually find configuration really nice with json auto completion. My config is here: https://github.com/ibraheemdev/dotfiles/tree/master/.vim https://github.com/ibraheemdev/dotfiles/tree/master/.vim.
    - ruph123 6y ago
      Thank you!
addcninblue 6y ago
Take a look at neovim 0.5 beta [0]. It has native support for LSP [1], and it's on par with other editors. Also, the setup is nearly zero overhead, as there are default configs [2] that others maintain. [0]: https://github.com/neovim/neovim https://github.com/neovim/neovim [1]: https://neovim.io/doc/user/lsp.html https://neovim.io/doc/user/lsp.html [2]: https://github.com/neovim/nvim-lspconfig https://github.com/neovim/nvim-lspconfig
jackric 6y ago
Curious about your thought process to leave VSCode for vim? I've been a long time vim user, but I've seemingly just surrendered to the ease of installing high quality extension in VScode. Just seems to work as advertised without me toiling in some config setup (vimrc) I use the Vim extension in VSCode for editing with my vim muscle memory, even though it has occasional snags/surprises
- skrtskrt 6y ago
  I really left IntelliJ (Python and Go) for Vim. I wanted to give Vim a good try anyway. My motivation was how ridiculously heavy IntelliJ is on resources I was doing Rust in VSCode and liked it but the Python support in VSCode was pretty terrible, and Go was so-so (Refactor/Rename tends to rename about 50% of the occurrences if you're lucky), so I wanted to try to concentrate everything in one editor. The downside for a language like Python without strong type system is the need to use the debugger super often, and I haven't gotten my command-line debugging chops up yet. The IntelliJ debugging experience is really, really nice.

ibraheemdev 6y ago

I use coc.nvim with rust-analyzer and I find it amazing. I used a more lightweight lsp client in the past, but I find the more full-featured coc.nvim to be the best balance - I get all the benefits of an IDE + the productivity of vim. coc is based on the VSCode intelli-sense engine and enables inline type-annotations by default, but I am not sure if "regular" vim (not neovim) supports it.

ruph123 6y ago
Can you please share your config? I find configuring coc quite painful.
- ibraheemdev 6y ago
  I actually find configuration really nice with json auto completion. My config is here: https://github.com/ibraheemdev/dotfiles/tree/master/.vim https://github.com/ibraheemdev/dotfiles/tree/master/.vim.
  - ruph123 6y ago
    Thank you!

addcninblue 6y ago

Take a look at neovim 0.5 beta [0]. It has native support for LSP [1], and it's on par with other editors. Also, the setup is nearly zero overhead, as there are default configs [2] that others maintain. [0]: https://github.com/neovim/neovim https://github.com/neovim/neovim [1]: https://neovim.io/doc/user/lsp.html https://neovim.io/doc/user/lsp.html [2]: https://github.com/neovim/nvim-lspconfig https://github.com/neovim/nvim-lspconfig

jackric 6y ago

Curious about your thought process to leave VSCode for vim? I've been a long time vim user, but I've seemingly just surrendered to the ease of installing high quality extension in VScode. Just seems to work as advertised without me toiling in some config setup (vimrc) I use the Vim extension in VSCode for editing with my vim muscle memory, even though it has occasional snags/surprises

skrtskrt 6y ago
I really left IntelliJ (Python and Go) for Vim. I wanted to give Vim a good try anyway. My motivation was how ridiculously heavy IntelliJ is on resources I was doing Rust in VSCode and liked it but the Python support in VSCode was pretty terrible, and Go was so-so (Refactor/Rename tends to rename about 50% of the occurrences if you're lucky), so I wanted to try to concentrate everything in one editor. The downside for a language like Python without strong type system is the need to use the debugger super often, and I haven't gotten my command-line debugging chops up yet. The IntelliJ debugging experience is really, really nice.