3 ms·
My main problem with vim was, that I spent deliberate effort to learn some of its shortcuts, but I need to use text editor in a console only a few times per wee
by greyman 6y ago
My main problem with vim was, that I spent deliberate effort to learn some of its shortcuts, but I need to use text editor in a console only a few times per week, like change some config file or add line to cronjob. And then one tends to forget all the shortcuts, when not using it regularly enough.
- wilsonnb3 6y agoMany IDEs and other editors have a vi-mode either built in or available as a plug in. I don’t use vim itself much (at work, at least) but I use vi keybindings everywhere.
- boring_twenties 6y agoWhich are your favorites? I have used the IdeaVim plugin for IntelliJ, and honestly it was so bad it was worse than not having the plugin at all. Maybe 20% of commands actually behaved consistently with vim. And IIRC, a decent chunk of my preferred vim functionality was outright unimplemented. Perhaps ironically, I didn't have any such problems with the (commercial) plugin for Visual Studio. It worked very well. It cost $100, but my employer paid for that. I've basically given up on IDEs after that and just use vim itself. If you know of any that have a really good vi-mode plugin, I'd love to try one!
- ralls_ebfe 6y agoEmacs has a pretty good vi mode called evil. I use spacemacs, but I am not sure, if it is what you are looking for. Should you try it, do yourself a favor and use the development branch. I read good things about doom Emacs as well.
- feanaro 6y agoYes, I think it only makes sense to learn vim if you're going to spend a lot of time using it actively. I use vim for almost all programming I do, so that made it really easy to burn it in my brain forever.