For example:įoo_bar, with the cursor at the f: df_ will Delete until it Finds an _, leaving you with bar. I have no intention of convincing you, if you're happy with VSCode keep on using it!īut Vim commands are very logical and consistent, so there's not much remembering to do.
Vim is amazingly powerful - but I can't be bothered to keep a map of key shortcuts in my brain. Stay safe 😄❤️ Like comment: Like comment: 10 likes Comment button Reply Collapse Expand It opens lots of doors, and just like the comments made here (by it's something that can take time doing, but once you get the basics, ""Īlso, I know there are other terminal editors too, if one stands out then pick that one! Whatever makes you the most productive is the best for you and that's really all that matters. Again, back to remoting into other machines, having an editor already there for you taking just a single config file and you're on your way is an amazing tool to have some skills with as a developer. I recommend learning some of the basics in navigation for developers of any kind. VIM is excellent, fast to use - especially when you start understanding the basics - and there is still so much more I don't know about it and have to learn but there's help with that (duh StackOverflow too).
#VISUAL STUDIO VIM PLUGIN INSTALL#
Even when VIM is not there, I install it, copy my dotfiles from GitHub, and continue with my day. Any time I'm remoting into a machine, I run vim. If I need things quick done now I run vim not vscode in my terminal to kick things off.
#VISUAL STUDIO VIM PLUGIN WINDOWS#
The majority of work is in VSC because it's pretty on the eyes, integrated terminal for Windows (because no global hotkeys for iTerm2 like macOS) and the ability to work on various instances - even in the browser (see GitHub's new Codespaces?). I often forget what functions are already implemented (or even the documentation and the argument variables) but that's when VSC is there holding my hand. Outside of the extensions, Intellisense is my saving grace. The extension list is ever-expanding, and with that, you're more likely to find a few that really work well for you, or even make your own. Once you have keybinding setup, a few environment configs, and runners, you're good to go. Editing on multiple devices gets annoying when switching over (Windows/macOS), but there are some plugins to help with that effort (search extension de-settings-sync). I sit within VSC almost all day every day. VSCode (VSC) and VIM are my two main editors.
0 kommentar(er)
