4 ms·

Let me back up a step here. I use VIM for almost all basic editing. Its muscle memory. But for code editing, I generally end up on VSCode because it seems to

Let me back up a step here. I use VIM for almost all basic editing. Its muscle memory. But for code editing, I generally end up on VSCode because it seems to have better language support. I've spent a fair amount of time with configuring VIM trying to get where I feel it needs to be. But whenever I shift to a new stack, it always seems to take an investment of time and effort to get VIM set where it's better than VSCode.

GrantZvolsky 6y ago
I share your experience, but it should only be a matter of time until the vim LSP clients[1] mature. One notable exception is Go with its [vim-go](https://github.com/fatih/vim-go https://github.com/fatih/vim-go) plugin, which feels very mature to me as someone new to the language. [1]: https://langserver.org/ https://langserver.org/
- deadbunny 6y ago
  CoC is already there: https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim
  - blandflakes 6y ago
    Having to install node.js for a language server client is sort of a downer. For this reason I've been eagerly awaiting the built-in client in neovim, though it's definitely less polished and feature-complete than CoC today.
    - deadbunny 6y ago
      Isn't the "built in" neovim language server lua? I personally can't see much difference between having to install nodejs runtime Vs the lua runtime.
      - igneo676 6y ago
        The difference is that the lua runtime is embedded (and wicked fast) into Neovim vs nodejs that has to go over the remote plugin interface
        deadbunny 6y ago
        Fair enough. I've been using coc for a while now and can't say I've ever had any speed issues that I've noticed. But if the neocvm language server is built in and "as good" as CoC then that'll be one less plugin I'll need to install when it's ready.
        blandflakes 6y ago
        Yeah I don't have any node.js speed concerns for it, I just would like to have the simplest editor microservice architecture, and putting the client to a service in a service was a bridge further than I wanted.
  - ogre_codes 6y ago
    CoC looks neat (installing right now), but it's a perfect example of what I mean. Having to poke through and add several dozen lines to my config file to get it working. I would love to have this functionality with just brew install ts-vim And just be done with it.
    - sooheon 6y ago
      I don't use vscode that much, but when I was checking it out I installed some extension which lets you edit text with true neovim (point it to a bianry) while vscode handles chrome and code understanding. Worked pretty well.
      - GrantZvolsky 6y ago
        You're probably talking about Neo Vim[1] by Alexey Svetliakov. I can't recommend this one enough for a (neo)vim experience in VS Code. It is relatively new and deserves a lot more attention. [1]: https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim https://marketplace.visualstudio.com/items?itemName=asvetlia...
        sooheon 6y ago
        Yeah that’s the one. Love that it’s not a half baked vim emulation.

GrantZvolsky 6y ago

I share your experience, but it should only be a matter of time until the vim LSP clients[1] mature. One notable exception is Go with its [vim-go](https://github.com/fatih/vim-go https://github.com/fatih/vim-go) plugin, which feels very mature to me as someone new to the language. [1]: https://langserver.org/ https://langserver.org/

deadbunny 6y ago
CoC is already there: https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim
- blandflakes 6y ago
  Having to install node.js for a language server client is sort of a downer. For this reason I've been eagerly awaiting the built-in client in neovim, though it's definitely less polished and feature-complete than CoC today.
  - deadbunny 6y ago
    Isn't the "built in" neovim language server lua? I personally can't see much difference between having to install nodejs runtime Vs the lua runtime.
    - igneo676 6y ago
      The difference is that the lua runtime is embedded (and wicked fast) into Neovim vs nodejs that has to go over the remote plugin interface
      - deadbunny 6y ago
        Fair enough. I've been using coc for a while now and can't say I've ever had any speed issues that I've noticed. But if the neocvm language server is built in and "as good" as CoC then that'll be one less plugin I'll need to install when it's ready.
        blandflakes 6y ago
        Yeah I don't have any node.js speed concerns for it, I just would like to have the simplest editor microservice architecture, and putting the client to a service in a service was a bridge further than I wanted.
- ogre_codes 6y ago
  CoC looks neat (installing right now), but it's a perfect example of what I mean. Having to poke through and add several dozen lines to my config file to get it working. I would love to have this functionality with just brew install ts-vim And just be done with it.
  - sooheon 6y ago
    I don't use vscode that much, but when I was checking it out I installed some extension which lets you edit text with true neovim (point it to a bianry) while vscode handles chrome and code understanding. Worked pretty well.
    - GrantZvolsky 6y ago
      You're probably talking about Neo Vim[1] by Alexey Svetliakov. I can't recommend this one enough for a (neo)vim experience in VS Code. It is relatively new and deserves a lot more attention. [1]: https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim https://marketplace.visualstudio.com/items?itemName=asvetlia...
      - sooheon 6y ago
        Yeah that’s the one. Love that it’s not a half baked vim emulation.