I still use vim as a plain text editor, and every once in a while I need to open a file in vim to do some serious macro editing (macros aren't perfectly supported by the plugin), but for the most part vscode+vimplugin is just nicer to use for day to day development. In vim, my experience was that I would lose a few hours to configuration, and the plugin would still be a little janky. You can add these keybindings to your init.vim if you are using the VSCode Neovim extension.
#VIM VSCODE CODE#
Visual Studio Code - Build and debug modern web and cloud applications. For me it destorys vscode for navigating a code base, with the proper setup (think i have 40+ plugins) and a lot of experience. Vim - Highly configurable text editor built to enable efficient text editing. Even macros work in VS Code, although they're just unusably slow for anything non-trivial. The plugin is an excellent option to try out another way of editing code and get a feel for it. When comparing quality of ongoing product support, reviewers felt. In this post, I share some tips about using the vim plugin in VSCode.
In vscode, I just search "rust" in extensions, grab the most popular one, and it sets itself up magically. Then as a vim user, your muscle memory sets in and you keep typing shit that doesn't work. Reviewers felt that Visual Studio Code meets the needs of their business better than Vim. The reason I switched is that plugins in vim are more of a pain to configure and they are usually less maintained and polished than their vscode equivalents.įor example, let's say I'm not set up to program rust at all. I absolutely use the vim plugin because I can't stand to edit text without vim keybindings anymore. Not the parent, but I switched from vim+plugins to vscode+plugins for most development.
0 kommentar(er)
