Hacker News Reader

Comment by 3fe9a03ccd14ca5 | Hacker News Reader

Better yet, install vscode, then install either the vim or emacs plugin. The best of all worlds!

Eh. Sort of. Like the other person who replied about the Emacs plugin, I find myself running into issues with the Vim plugin -- usually not the keybindings as much as the ex-style commands. For instance, ":20,27m." will move a block of text in Vi/Vim to under the current location; that doesn't work in VSCode Vim. Worse for me personally, I've gotten really used to the ":find" command being the (rough) equivalent of a fuzzy file search: ":find App.php" will find that file no matter where it is in the current project, but again, not a VSCode Vim command.

It's a good emulation, but it's not a great emulation.

Ctrl+p will let you search nicely for files in vscode. At least the VI integration is better than the extension I use with Visual Studio.

Oh, yeah, I do use that (well, Cmd-P over here in Mac-world). It's just when I get into Vim mode I type ":find" reflexively and I get disappointed for a moment. :)

(Ironically, there's a Vim plugin called CtrlP to do the same thing that I never use because I find it confusing and weird compared to everybody else's implementation of the same idea...)

Kind of. I haven't found a VSCode emacs package that does more than superficially handle emacs keybindings; there's always mismatches that trip me up.

Reply on news.ycombinator.com