3 ms·
> vi clones This is the problem with moving off vi motions: you can get vi motions almost everywhere. Jetbrains, check, Visual Studio, check, vscode, check, su
by zamalek 3y ago
> vi clones
This is the problem with moving off vi motions: you can get vi motions almost everywhere. Jetbrains, check, Visual Studio, check, vscode, check, sublime, check, firefox, check. The best I found for Kakoune (which I do significantly prefer) was an approximation of it for vscode, and nothing else.
- bee_rider 3y agoI tried vim bindings in VSCode but I couldn’t stand them, it was right inside the uncanny valley for me.
- Sirenos 3y agoWhat didn't you like about it?
- bee_rider 3y agoTypically I use vim+tmux, so I should have also probably set up some additional extension to add a tmux-like panel change shortcut, so I could save-and-run like I normally would on the command line. It also didn’t seem to handle Jupyter cells well. I forget exactly, but sometimes it would jump from one panel to another instead I think?
- the_gipsy 3y agoThere is always something once in a while that steals the focus from the text and forces you to click back.