4 ms·
I jump back and forth between using keyboard & mouse when working on a IDE and vim when working on terminal. While I could just hook up a vim plugin that is pr
by flykespice 2y ago
I jump back and forth between using keyboard & mouse when working on a IDE and vim when working on terminal.
While I could just hook up a vim plugin that is present on almost all IDEs, I debilatery chose not to because they feel ucanny since many vim bindings conflict with the IDE default bindings and their intregation don't work well. It's better suited as standalone application.
- koakuma-chan 2y agoVim plugins are generally unusable. The one that VSCode has is especially bad.
- sceadu 2y agothe vim one is pretty irritating with input delay but the neovim one isn't too bad (the one that hooks into neovim)... at least it makes vs code tolerable enough for me so I don't bang my head against the wall when I have to use it
- weaksauce 2y agouse the neovim one ... it's actual vim + vscode.
- koakuma-chan 2y agoNo thanks, I would rather code in terminal. I can't stand using an Electron app.
- weaksauce 2y agook but that is just moving the goalpost from the plugins are crap to i don't like electron. idc what you do but for anyone that wants vscode with vim bindings the neovim ones are great.