4 ms·

I love vim modal keybindings more than Vim, I don't really use actual vim much at all, certainly not for coding. Luckily most editors / IDEs have Vim support

bee_rider 4y ago
I can't stand the Vim plugin in VSCode, it is this awful uncanny valley thing. I'd rather just abandon all hope and get it over with.
- revicon 4y ago
  This was my experience as well. I really tried to use the vim plugin for vscode but there were too many behavior differences between it and native vim. And VSCode just has too many features that I've grown to love that I just find myself learning the native VSCode bindings and using those most of the time now. I miss VIM, I really do, but I really only use it these days if I need to ad-hoc modify an individual file while I'm in a terminal somewhere.
  - mcluck 4y ago
    You can bind VS Code commands to vim-style commands. I have plenty of VS Code specific features bound to leader-based commands
- another_story 4y ago
  Are you using the plugin backed by Neovim or the other one? https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim https://marketplace.visualstudio.com/items?itemName=asvetlia...
  - scruple 4y ago
    I use it but it's typically a source of problems to the point that I have to save everything and restart my session. You can have very, very little custom neovim configuration present. My vimrc checks if it's inside of VSCode and does nothing but I still frequently encounter problems. Weekly, at the very least. I'd love to get outside of VSCode fulltime but where I work today uses Docker for development and it's a complete pain in the ass to connect text editor plugins with services running on a remote host. VSCode has this out of the box, so it wins. My next job, I'll be sure to press for this level of detail about the development experience.
- mcluck 4y ago
  I've heard plenty of people say this and I just don't understand it. I use vim bindings in VS Code 95% of the time but the 5% of the time that I use real vim, it all works exactly the same
  - nucleardog 4y ago
    How deep have you gone into vim? Admittedly it's been a while since I tried vscode, but when I did my experience was that vim's functionality is a superset of what's available in the plugin. Especially if you learned on the plugin, vim would generally work the same as vscode. The issue was the other way--there was functionality missing in the plugin, or sometimes when you tried to compose more complex operations they didn't work or worked strangely, etc. Like, if you're used to working in C you won't see the advantage of a C++ compiler, but if you've spent 15 years working in C++, you're gonna feel pretty hamstrung by a C compiler.
    - mcluck 4y ago
      Can you give me an example of something that doesn't work correctly? I'm not an expert but I'm pretty sure I know all of the movements and basic verbs and they all seem to work fine to me. I believe you that there are missing features but I'm wondering what I'm missing out on
      - bee_rider 4y ago
        I've got the VSCodeVim extension installed, some other people have mentioned one that is backed by the neovim folks so maybe that one is better. imap/nmap don't seem to work -- I think I'm an intermediary vim user in the sense that I don't have all the shortcuts memorized. So it can be useful to just throw together a macro to encode an idea like "change the parentheses to brackets around this variable and then go to the next search result." I'm sure there's a built-in command for this sort of thing but I don't have it memorized, so what I'll sometimes do is just perform the transformation manually once, keep track of which keys I hit, and then nmap that to some random key. Before, my gripe was that visual mode didn't work, but they added that (yay!).

bee_rider 4y ago

I can't stand the Vim plugin in VSCode, it is this awful uncanny valley thing. I'd rather just abandon all hope and get it over with.

revicon 4y ago
This was my experience as well. I really tried to use the vim plugin for vscode but there were too many behavior differences between it and native vim. And VSCode just has too many features that I've grown to love that I just find myself learning the native VSCode bindings and using those most of the time now. I miss VIM, I really do, but I really only use it these days if I need to ad-hoc modify an individual file while I'm in a terminal somewhere.
- mcluck 4y ago
  You can bind VS Code commands to vim-style commands. I have plenty of VS Code specific features bound to leader-based commands
another_story 4y ago
Are you using the plugin backed by Neovim or the other one? https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim https://marketplace.visualstudio.com/items?itemName=asvetlia...
- scruple 4y ago
  I use it but it's typically a source of problems to the point that I have to save everything and restart my session. You can have very, very little custom neovim configuration present. My vimrc checks if it's inside of VSCode and does nothing but I still frequently encounter problems. Weekly, at the very least. I'd love to get outside of VSCode fulltime but where I work today uses Docker for development and it's a complete pain in the ass to connect text editor plugins with services running on a remote host. VSCode has this out of the box, so it wins. My next job, I'll be sure to press for this level of detail about the development experience.
mcluck 4y ago
I've heard plenty of people say this and I just don't understand it. I use vim bindings in VS Code 95% of the time but the 5% of the time that I use real vim, it all works exactly the same
- nucleardog 4y ago
  How deep have you gone into vim? Admittedly it's been a while since I tried vscode, but when I did my experience was that vim's functionality is a superset of what's available in the plugin. Especially if you learned on the plugin, vim would generally work the same as vscode. The issue was the other way--there was functionality missing in the plugin, or sometimes when you tried to compose more complex operations they didn't work or worked strangely, etc. Like, if you're used to working in C you won't see the advantage of a C++ compiler, but if you've spent 15 years working in C++, you're gonna feel pretty hamstrung by a C compiler.
  - mcluck 4y ago
    Can you give me an example of something that doesn't work correctly? I'm not an expert but I'm pretty sure I know all of the movements and basic verbs and they all seem to work fine to me. I believe you that there are missing features but I'm wondering what I'm missing out on
    - bee_rider 4y ago
      I've got the VSCodeVim extension installed, some other people have mentioned one that is backed by the neovim folks so maybe that one is better. imap/nmap don't seem to work -- I think I'm an intermediary vim user in the sense that I don't have all the shortcuts memorized. So it can be useful to just throw together a macro to encode an idea like "change the parentheses to brackets around this variable and then go to the next search result." I'm sure there's a built-in command for this sort of thing but I don't have it memorized, so what I'll sometimes do is just perform the transformation manually once, keep track of which keys I hit, and then nmap that to some random key. Before, my gripe was that visual mode didn't work, but they added that (yay!).