5 ms·
> I never bothered installing plugins and spent all my time instead learning This wisdom should be shared with everyone learning vi/vim, since this leads direc
by dwc 15y ago
> I never bothered installing plugins and spent all my time instead learning
This wisdom should be shared with everyone learning vi/vim, since this leads directly to the largest payoff.
- derwiki 15y agoI dunno, Command-T was a pretty big boon to my productivity (https://github.com/wincent/Command-T https://github.com/wincent/Command-T).
- leviathan 15y agoThe general idea is that if your productivity relies on external plugins, it will drop very low as soon as you have to use someone else's machine, or when you have to work with lots of various systems where setting up your environment isn't an option.
- ulisesrmzroche 15y agoI think it's more that everyone is taking the bus to Abilene. Can you explain the first point a bit more? On the second point, you can always :e scp if you need to. I've never maintained my own .vimrc, or know what plugins I have installed or not, btw.
- dwc 15y agoI don't mean to say that you shouldn't find and use plugins, because there are some really great ones that answer real needs. But it seems that a lot of people new to vim get distracted by plugins, tweaking their config, et al, when they could be learning the "vi way" to get their actual code editing productivity.
- wahnfrieden 15y agoI disagree to some extant. I've been a power use for more than a decade and some of the default ways of doing things are just wrong. It is true though that people are reluctant to learn about what vim itself already provides - more people should use the fantastic help system (once you know the basics) rather than rely on blog posts for everything, too.
- AlexCP 15y agoThere are some extremely powerful and useful plugins, CommandT for example, that shouldn't be miss.
- gnosis 15y agoIf you don't use plugins, you are really missing out. Check out PreciseJump and EasyMotion: http://www.vim.org/scripts/script.php?script_id=3437 http://www.vim.org/scripts/script.php?script_id=3437 http://www.vim.org/scripts/script.php?script_id=3526 http://www.vim.org/scripts/script.php?script_id=3526 (watch the animated gif demos on those pages and be amazed!) MRU is really useful for navigating the most recently opened files: http://www.vim.org/scripts/script.php?script_id=521 http://www.vim.org/scripts/script.php?script_id=521 xptemplate is an awesome, very advanced snippet plugin: http://www.vim.org/scripts/script.php?script_id=2611 http://www.vim.org/scripts/script.php?script_id=2611 NerdCommenter, for easy commenting/uncommenting blocks of code: http://www.vim.org/scripts/script.php?script_id=1218 http://www.vim.org/scripts/script.php?script_id=1218 And, of course, before you install any plugin, you should do yourself a favor and install and use Pathogen, or something like it: http://www.vim.org/scripts/script.php?script_id=2332 http://www.vim.org/scripts/script.php?script_id=2332 For me, these are some of the most essential plugins that I use every day. Some other good ones are tabular, renumber, stripansi, matchit, and surround.
- roel_v 15y agoHow long have you been using vim?
- gnosis 15y agoDecades.
- sohooo 15y agoI'm also a fan of Pathogen (and tpope's stuff in general), but now I would recommend Vundle. It's like Ruby's Bundler for Vim. The difference is that you define the bundles (plugins) you want to use right in your .vimrc. With :BundleInstall/:BundleUpdate clones/updates these plugins. https://github.com/gmarik/vundle https://github.com/gmarik/vundle
- gnosis 15y agoI'm not really sold on vundle (or other plugins like it). I don't really like the automation it provides. I'd much rather just install stuff by hand in to ~/.vim/bundle and do my own updates. That way I have maximum control and full knowledge of what's going on in the install process.