I'd add to that to try and start using neovim. I've switched to it on Mac without a hitch and we (Floobits) have already moved our vim plugin to use the new neovim python-client plugin for much better async behavior. Making an async plugin for NeoVim is pretty trivial, here's a clock in your status bar:
Note this requires +python, :he nvim-python for how to get that (involves pip install neovim)
You can't do something like this clock in vim without the feed keys cursorhold hack that breaks using leader keys. Otherwise I'm still using vundle and have made 0 changes in my .vimrc other than move it all to .nvim and .nvimrc. All my plugins and vundle worked out of the box.
I had put neovim out of mind and settled for emacs/evil, but seeing an actual use case for the new plugin system makes me hopeful for it's fast growth and adoption.
Does vanilla neovim offer anything that a vanilla vim user might like? I imagine I will make the switch at some point, I just wonder if there's any compelling reason to do so sooner rather than later.
I agree. I initially found many recommendations to bind "," as leader, and it was convenient, but after learning what ";" and "," do, I've changed my leader to <space>.
I have a hard time understanding vim users. All the cool features listed in this article exist in any modern text editor. I personally use Notepad++, but I'm sure the same goes for Textmate, Sublime Text and many others.
The only advantage I can see in Vim over a modern solution is that it runs in the terminal (which I guess is useful if you like to remotely modify files in your production environment?). Is it that after they have spent so many years learning the arcane controls, users feel obligated to stick with it in order to justify all the time they've already invested?
I must say I've only spent ~2 months of my life using vim before giving up, which I think is already pretty long for an evaluation. I have never experienced or even witnessed the productivity gains you're supposed to get from mastering vim. All I've seen is very unintuitive shortcuts for Ctrl+Backspace advertised as unique features in the world of text editing.
I would be very happy if someone could point out to me the elephant that I am not seeing here.
The stuff listed in this article are the places where Vim was trying to catch up with modern editors, not where Vim excels. Vim is an old editor, for modern features, Vim has been the one that's catching up, and luckily it did. But that has nothing do with why people love Vim.
Vim, in pure code editing sense, has two unique advantages that no other editors have or dare to have: modal editing and ubiquity.
Modal editing makes code editing absolutely DRY, as users can avoid any repetitive typing/clicking that they wish to avoid. It doesn't necessarily increase your code throughput much as a lot of the time you'll be thinking instead of typing, but it reduces the frustration of editing to almost zero when you do have to type, hence reducing distractions and cognitive load. Once you are familiar with Vim, its commands have close to one-to-one mapping to ANY ways you want to edit code.
For example, you want to change the html text two lines above? kkcit. Then come back to the place where you left? g;g;. Re-indent the lines? =ip. They look foreign and unintuitive to non-vim users, but are actually muscle memories for vim users. This is probably why vim users swear by it, but non-users find it hard to love.
Ubiquity is something you can only appreciate when you have to. If your work environment is Windows, this probably won't occur to you. But if you have to code in different OSes, or in SSH sessions, or in git commit, or in less/man commands, you'll find vim invaluable.
After all, Vim is just a tool, a very good one. But if your work doesn't have the need for it, you won't find it useful.
There is no elephant in the room. Vim will not make you more productive, period. Vim unequivocally takes the fewest keystrokes to effect changes, but its certainly not the fastest editor. At Floobits, we sometimes have 3 devs working on the same code at the same time (normally when something goes really wrong). When ggreer is around, he is always the fastest to edit text bar none. He uses ST3 and a trackpad. If someone is using some Intellij (PyCharm, Idea), that person is the fastest and safest at refactoring bar none.
It may be true that some magical Vim invocation is the fewest key strokes in any text editor to edit text. In practice real world Vim users probably lose just as much time as they save trying to find the magical incantation. Beyond saving a few keystrokes, consider how wasteful it is to devote months of effort learning a new text editor when editing text is such a small fraction of the time we spend programming. Are programmers ever limited by how quickly we can type? No, we are limited by how quickly we can think!
Having said that, NeoVim is a fairly decent choice for a text editor. It is open source, runs in a terminal, is actively developed, and (vim) is installed on nearly every *nix by default.
Former longtime emacs (and previous to that, vi) user here.
vi and emacs seem like magic if you're coming from something like SublimeText. Compared to modern IDEs like VisualStudio or IntelliJ products, however - not so much.
vi users tout the rapid text editing features, but you can generate and navigate code just as fast with an IDE - out of the box - no configuration incantations or third party packages required.
Until very recently (early to mid-2000s), IDEs for open source web frameworks were non-existent, unaffordable, or slow. Once you have a working vi or emacs setup, there's a lot of inertia in place that discourages switching.
That explains the continued popularity of vi, imo.
Vim is a Linux/Unix text editor used via the terminal. Notepad++ is for the Windows GUI environment. Apples and Oranges.
Why is a good terminal text editor important? When you are SSH'ed into your server and you need to adjust a configuration file, you require a good terminal text editor. It also is very good for C programming, and a lot of C programmers use it extensively. There are many other reasons. From a Windows GUI environment, you won't really be able to compare or relate, or understand why vim is so good.
"I would be very happy if someone could point out to me the elephant that I am not seeing here."
The one thing where vim beats hands down any vanilla text editor, such as you have listed, is the speed of text editing facilitated by its mode-based usage paradigm. It's not the number of features, but the pure effortlessness of the frequently used editing actions vim offers.
The technical details are detailed in many vim tutorials. The speed comes from the fact that for a large set of common non trivial operations there is a one or two key sequence that establishes the precise edit you wanted.
The way to discover these actions needs a bit of self conscious learning: You notice you do something repeatedly (sometimes painfully obviously) and figure out if there is a quick set of operations in vim to do the thing you wanted to do.
To get the full power of vim you need to spend enough time with it so the frequent editing actions you want to achieve are automatically decomposed in your backbone to vim operations, at which point you can edit text at the speed of tought.
Also, the split window dual or triple document editing combined with fast commands for switching to different places in the documents is really nice.
Once you're good at vim you can edit at the speed of thought. Not really much better way to put it. Watching non-vim users edit text is eternally frustrating.
It doesn't increase throughput much because most of the time editing/typing is not the bottleneck. Thinking is.
But it is frustrating to reach for mouse and click several times for a task that can be easily done quickly with keyboard. In another words, it interrupts the flow.
> The only advantage I can see in Vim over a modern solution is that it runs in the terminal (which I guess is useful if you like to remotely modify files in your production environment?).
ssh -X host
Then remotely run whatever tool you want, including Sublime or Geany or Kate or even Wireshark if you wish.
> I must say I've only spent ~2 months of my life using vim before giving up, which I think is already pretty long for an evaluation.
Hmm yeah that is pretty long, you should see the advantage of it by then. Have you used it a lot in those two months? Because I've alternated between Geany and vim for like 6 months before being fluent enough in vim that I could get work done at the speed I could in Geany (or Notepad++ for that matter). But if I had seriously used vim for everything that I used Geany for, I think I would have easily gotten there in 2 months.
> I would be very happy if someone could point out to me the elephant that I am not seeing here.
Beyond that it's simply faster in text editing (code, plain text, or something like Markdown for that matter), I guess it's also a way of using a computer. I've never liked the mouse for anything besides games or GIMP and even navigate many websites by keyboard in Firefox. Ideally I'd spend all my time in a terminal, typing away with my hands almost never leaving the home row. But that's just me, I know noone else who is so fond of their keyboard vs. a mouse or touchpad.
This is coming from someone that used IntelliJ before moving to Sublime Text 3 before moving to vim for Python development.
I am by no means a master of vim's varied features but the best productivity gain for me is vim running in the terminal. I use a lot of command line tools (grep still beats most things for search and the git command line tool is still better than any editor plugins), it's just much more convenient for me when it's all in the terminal and I can switch between them seamlessly with keyboard commands especially when using something like tmux.
I used vi, vim and was an Emacs user between 1996 and 2005 when coding on UNIX platforms.
But I have came to UNIX from the home computers, so I was already spoiled with Borland IDEs and Amiga editors before my first UNIX experience.
Got to experience Smalltalk and Oberon environments as well.
Always looked for IDE experiences in UNIX land, and since I moved 100% into JVM/CLR land, I only use Emacs or VIM for editing configuration files or when on systems where my beloved IDEs aren't available.
Even for C++, thanks to LLVM work, IDEs can offer much more that vi or emacs do, even with CEDET.
Flexibility, configurability, work in the terminal, oh... and did I mention snipmate?
That's just scratching the surface. I've been using VIM for around 3 years. Most of the day almost every day. And I feel like I'm barely acquainted with what it can do. Still, it is one of the most important and vital work tools and its hard to imagine life without it. I'm pretty sure I would leave any job I wasn't allowed to use it.
Admittedly I went through a rough month or two getting started, but I could see right away that the potential gains in productivity were worth the cost and I'm glad I did. Sort of like learning to type which some people refuse to do because hunting and pecking is faster and easier short term. I'm sure you have seen people like this. And some actually type at amazing speeds for two fingers, but it doesn't compare with what they could do if they took the time to retrain themselves.
The problem now is that Vim is so ingrained in muscle memory I type splotch all over any other editor and web browser I touch. Hold on a second, I need to arrow back and clean up this comment... bbbbhhh
I absolutely hate having to lift one of my hand off the keyboard to grab the mouse. Vim's text navigation is the top killer feature that all modern editor are lagging behind.
The second one is modal mode (editing and navigating/command).
I am trying to warm up to ST and the vim plugin is okay but some things are really missing (capital R)
It's not about speed. It's about finding the vocabulary of vim natural (which it seems you don't, which is fine). 'di(' for instance deletes the inside of parentheses. Which is a natural action to perform, if your cursor is inside parentheses.
The key feature in vim for me is that I never have to move my fingers from the typing position on the keyboard. I never have to look away to find the home key or the arrow keys.
All the things mentioned in the article are just there to not miss the nice features of other editors.
There're things I agree or disagree on with author (for example, I still have NerdTree installed, but find myself almost never using it, instead I use tree -f in separate terminal window) but probably only one thing I'm still not sure about:
I don't use buffers explicitly at all, only tabs instead, like in any IDE. Sometimes vsplit. I even have custom mappings for ctags to open stuff in new tabs instead of buffers. I treat hidden buffers as legacy needed mostly for technical reasons. Yet I keep seeing other people using multiple buffers, switching between them. So, should I reconsider, maybe? And why?
I used tabs, but nowadays I don't seem to need them. One day I thought I could try if I could survive by just using buffers, and apparently I do. Might depend on the way you want to navigate the project and so on. For me personally the most common buffer switch is between two or three documents at a time and for those needs split windows are absolutely the best for me (which removes any needs for tabs, naturally).
The switch to tabs for me came after I started using vimperator/pentadactyl in my web browser, which I find glorious. (Sorry no links, on mobile)
I used "lusty juggler" before but 'gt' is a very natural way for me to "go tab" now and I like it better. Macvim makes it trivial for me to arrange tabs in a consistent order, for example html file to the left of its js file. The tabs also give me a kind of quick view of what my current "project space" is.
Two tab-y things that I find useful are:
* alias "vi -p" (to open files in tabs)
* "vi --remote-tab" (to add a file to an existing session in a new tab from the command line)
Part of why I like tabs may be because I don't do split windows often in vim. When I want to have two files side-by-side I use my os window manager (CMD+right to move current window to right side of screen, etc).
I wanted to like unite, but couldn't get it to behave as I expected: when opening a file via unite, it doesn't respect the active window, it ignores the splits I have. IIRC it always opened the file in the top left window.
I've found split windows and buffers in vanilla vim to be somewhat lacking -- CtrlSpace [1] and GoldenView [2] plugins are truly awesome enhancements. The latter I wish I could have at the OS level, just incredibly efficient usage of screen real estate, and the former makes buffer management a breeze.
> Emacs has a useful mode which highlights hexidecimal colors in CSS and SASS
There's plugin for it in vim. Even several of them, as always. I don't remember which one I used and if it was completely ok, but I can find https://github.com/skammer/vim-css-color right away.
Thanks for reading! Don't forget to check out the follow-up to this article, "Everything I Missed in Vim After 11 Years" - http://statico.github.io/vim2.html
Another person who recommends pathogen... There's multiple better plugin managers now including Neobundle and vundle... I find neobundle to be unquestionably superior and well worth using.
They aren't "better" and most of pathogen users are well aware of them. I don't think they are bad enough to discourage anyone from using them if it woks for him, but when asked I'm always recommending pathogen as the only option, which I'm using myself.
Why? Well, there could be multiple answers, but essentially there's one main reason: it's just dead simple, while vundle and other ruby-inspired ones are not. Pretty much for the same reason I like pathogen+git thousand times more than emacs' package manager.
So even if it could be arguable that pathogen is better than vundle, there's completely no reason not to advise it.
I also prefer using the terminal, but I've switched to neovim anyway. I found macvim to be difficult to configure and I just prefer having tmux terminal splits next to my vim split and I can see stuff happening as I edit the file. I also prefer iTerm2 to Terminal.app but I think it's just personal preference. I know how to use the iTerm2 settings pretty well by now to get configurations I want.
For me it's definitely mouse reporting. If my hand is already on the mouse I really like clicking tmux panes. Sometimes it's also easier to just scroll with a trackpad too.
Apropos of nothing in particular: a good way of spotting vim hipsters is that they don't know what ; does, because they never used t or f. They do however very carefully use hjkl to move around, because the cursor keys are for squares ;)
I remapped ; a long time ago (to ":", because I can't be bothered to hold down the shift key) because I rarely need to repeat a t/T/f/F motion. I typically already know how many times I need to invoke it (and use "3f)" for example), or I use a quick "/" followed by a couple of letters in the word I want to jump to.
In my experience nerdtree is bad. You loose a lot of goodnes that splits can offer you. Netrw or netrw+vinegar is more vim friendly way to do file navigation.
[+] [-] btipling|11 years ago|reply
https://gist.github.com/btipling/0d6faa80b24ccee5caea
Note this requires +python, :he nvim-python for how to get that (involves pip install neovim)
You can't do something like this clock in vim without the feed keys cursorhold hack that breaks using leader keys. Otherwise I'm still using vundle and have made 0 changes in my .vimrc other than move it all to .nvim and .nvimrc. All my plugins and vundle worked out of the box.
[+] [-] sooheon|11 years ago|reply
[+] [-] Gracana|11 years ago|reply
[+] [-] pmoriarty|11 years ago|reply
The original binding of ; is super useful, and I would argue it should not be rebound.
; repeats the last f, t, F or T command.
There's also , which is the same as ; but in the opposite direction.
[+] [-] sooheon|11 years ago|reply
[+] [-] lucb1e|11 years ago|reply
The only thing I never understood was why ; doesn't go beyond the current line (n does). Is there a way to make it?
[+] [-] placeybordeaux|11 years ago|reply
[+] [-] agersant|11 years ago|reply
The only advantage I can see in Vim over a modern solution is that it runs in the terminal (which I guess is useful if you like to remotely modify files in your production environment?). Is it that after they have spent so many years learning the arcane controls, users feel obligated to stick with it in order to justify all the time they've already invested?
I must say I've only spent ~2 months of my life using vim before giving up, which I think is already pretty long for an evaluation. I have never experienced or even witnessed the productivity gains you're supposed to get from mastering vim. All I've seen is very unintuitive shortcuts for Ctrl+Backspace advertised as unique features in the world of text editing.
I would be very happy if someone could point out to me the elephant that I am not seeing here.
[+] [-] zefei|11 years ago|reply
Vim, in pure code editing sense, has two unique advantages that no other editors have or dare to have: modal editing and ubiquity.
Modal editing makes code editing absolutely DRY, as users can avoid any repetitive typing/clicking that they wish to avoid. It doesn't necessarily increase your code throughput much as a lot of the time you'll be thinking instead of typing, but it reduces the frustration of editing to almost zero when you do have to type, hence reducing distractions and cognitive load. Once you are familiar with Vim, its commands have close to one-to-one mapping to ANY ways you want to edit code.
For example, you want to change the html text two lines above? kkcit. Then come back to the place where you left? g;g;. Re-indent the lines? =ip. They look foreign and unintuitive to non-vim users, but are actually muscle memories for vim users. This is probably why vim users swear by it, but non-users find it hard to love.
Ubiquity is something you can only appreciate when you have to. If your work environment is Windows, this probably won't occur to you. But if you have to code in different OSes, or in SSH sessions, or in git commit, or in less/man commands, you'll find vim invaluable.
After all, Vim is just a tool, a very good one. But if your work doesn't have the need for it, you won't find it useful.
[+] [-] kansface|11 years ago|reply
It may be true that some magical Vim invocation is the fewest key strokes in any text editor to edit text. In practice real world Vim users probably lose just as much time as they save trying to find the magical incantation. Beyond saving a few keystrokes, consider how wasteful it is to devote months of effort learning a new text editor when editing text is such a small fraction of the time we spend programming. Are programmers ever limited by how quickly we can type? No, we are limited by how quickly we can think!
Having said that, NeoVim is a fairly decent choice for a text editor. It is open source, runs in a terminal, is actively developed, and (vim) is installed on nearly every *nix by default.
[+] [-] brandonmenc|11 years ago|reply
vi and emacs seem like magic if you're coming from something like SublimeText. Compared to modern IDEs like VisualStudio or IntelliJ products, however - not so much.
vi users tout the rapid text editing features, but you can generate and navigate code just as fast with an IDE - out of the box - no configuration incantations or third party packages required.
Until very recently (early to mid-2000s), IDEs for open source web frameworks were non-existent, unaffordable, or slow. Once you have a working vi or emacs setup, there's a lot of inertia in place that discourages switching.
That explains the continued popularity of vi, imo.
[+] [-] Alupis|11 years ago|reply
Vim is a Linux/Unix text editor used via the terminal. Notepad++ is for the Windows GUI environment. Apples and Oranges.
Why is a good terminal text editor important? When you are SSH'ed into your server and you need to adjust a configuration file, you require a good terminal text editor. It also is very good for C programming, and a lot of C programmers use it extensively. There are many other reasons. From a Windows GUI environment, you won't really be able to compare or relate, or understand why vim is so good.
[+] [-] fsloth|11 years ago|reply
The one thing where vim beats hands down any vanilla text editor, such as you have listed, is the speed of text editing facilitated by its mode-based usage paradigm. It's not the number of features, but the pure effortlessness of the frequently used editing actions vim offers.
The technical details are detailed in many vim tutorials. The speed comes from the fact that for a large set of common non trivial operations there is a one or two key sequence that establishes the precise edit you wanted.
The way to discover these actions needs a bit of self conscious learning: You notice you do something repeatedly (sometimes painfully obviously) and figure out if there is a quick set of operations in vim to do the thing you wanted to do.
To get the full power of vim you need to spend enough time with it so the frequent editing actions you want to achieve are automatically decomposed in your backbone to vim operations, at which point you can edit text at the speed of tought.
Also, the split window dual or triple document editing combined with fast commands for switching to different places in the documents is really nice.
Notepad++ is my second editor of choice as well.
[+] [-] gfodor|11 years ago|reply
[+] [-] sohooo|11 years ago|reply
[+] [-] netheril96|11 years ago|reply
But it is frustrating to reach for mouse and click several times for a task that can be easily done quickly with keyboard. In another words, it interrupts the flow.
[+] [-] lucb1e|11 years ago|reply
ssh -X host
Then remotely run whatever tool you want, including Sublime or Geany or Kate or even Wireshark if you wish.
> I must say I've only spent ~2 months of my life using vim before giving up, which I think is already pretty long for an evaluation.
Hmm yeah that is pretty long, you should see the advantage of it by then. Have you used it a lot in those two months? Because I've alternated between Geany and vim for like 6 months before being fluent enough in vim that I could get work done at the speed I could in Geany (or Notepad++ for that matter). But if I had seriously used vim for everything that I used Geany for, I think I would have easily gotten there in 2 months.
> I would be very happy if someone could point out to me the elephant that I am not seeing here.
Beyond that it's simply faster in text editing (code, plain text, or something like Markdown for that matter), I guess it's also a way of using a computer. I've never liked the mouse for anything besides games or GIMP and even navigate many websites by keyboard in Firefox. Ideally I'd spend all my time in a terminal, typing away with my hands almost never leaving the home row. But that's just me, I know noone else who is so fond of their keyboard vs. a mouse or touchpad.
[+] [-] super_mario|11 years ago|reply
http://www.viemu.com/a-why-vi-vim.html
http://stackoverflow.com/questions/1218390/what-is-your-most...
The elephant you are missing is UNIX itself. The best IDE ever made.
[+] [-] ayrx|11 years ago|reply
I am by no means a master of vim's varied features but the best productivity gain for me is vim running in the terminal. I use a lot of command line tools (grep still beats most things for search and the git command line tool is still better than any editor plugins), it's just much more convenient for me when it's all in the terminal and I can switch between them seamlessly with keyboard commands especially when using something like tmux.
[+] [-] pjmlp|11 years ago|reply
I used vi, vim and was an Emacs user between 1996 and 2005 when coding on UNIX platforms.
But I have came to UNIX from the home computers, so I was already spoiled with Borland IDEs and Amiga editors before my first UNIX experience.
Got to experience Smalltalk and Oberon environments as well.
Always looked for IDE experiences in UNIX land, and since I moved 100% into JVM/CLR land, I only use Emacs or VIM for editing configuration files or when on systems where my beloved IDEs aren't available.
Even for C++, thanks to LLVM work, IDEs can offer much more that vi or emacs do, even with CEDET.
[+] [-] jqm|11 years ago|reply
That's just scratching the surface. I've been using VIM for around 3 years. Most of the day almost every day. And I feel like I'm barely acquainted with what it can do. Still, it is one of the most important and vital work tools and its hard to imagine life without it. I'm pretty sure I would leave any job I wasn't allowed to use it.
Admittedly I went through a rough month or two getting started, but I could see right away that the potential gains in productivity were worth the cost and I'm glad I did. Sort of like learning to type which some people refuse to do because hunting and pecking is faster and easier short term. I'm sure you have seen people like this. And some actually type at amazing speeds for two fingers, but it doesn't compare with what they could do if they took the time to retrain themselves.
The problem now is that Vim is so ingrained in muscle memory I type splotch all over any other editor and web browser I touch. Hold on a second, I need to arrow back and clean up this comment... bbbbhhh
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] johnchristopher|11 years ago|reply
The second one is modal mode (editing and navigating/command).
I am trying to warm up to ST and the vim plugin is okay but some things are really missing (capital R)
[+] [-] hedning|11 years ago|reply
[+] [-] JelteF|11 years ago|reply
All the things mentioned in the article are just there to not miss the nice features of other editors.
[+] [-] krick|11 years ago|reply
I don't use buffers explicitly at all, only tabs instead, like in any IDE. Sometimes vsplit. I even have custom mappings for ctags to open stuff in new tabs instead of buffers. I treat hidden buffers as legacy needed mostly for technical reasons. Yet I keep seeing other people using multiple buffers, switching between them. So, should I reconsider, maybe? And why?
[+] [-] fsloth|11 years ago|reply
[+] [-] alanning|11 years ago|reply
I used "lusty juggler" before but 'gt' is a very natural way for me to "go tab" now and I like it better. Macvim makes it trivial for me to arrange tabs in a consistent order, for example html file to the left of its js file. The tabs also give me a kind of quick view of what my current "project space" is.
Two tab-y things that I find useful are:
* alias "vi -p" (to open files in tabs)
* "vi --remote-tab" (to add a file to an existing session in a new tab from the command line)
Part of why I like tabs may be because I don't do split windows often in vim. When I want to have two files side-by-side I use my os window manager (CMD+right to move current window to right side of screen, etc).
[+] [-] unknown|11 years ago|reply
[deleted]
[+] [-] krick|11 years ago|reply
Actually it is. That thing is called "leader" and is used exactly for the same purpose as author uses backslash. So better way to write
would be Reasons to use "leader" are discussed more than once, so I'll leave reading the docs/blogposts to you.[+] [-] shocks|11 years ago|reply
I prefer unite[1] to ctrl-p[2], it's much more flexible.
1: https://github.com/Shougo/unite.vim 2: https://github.com/kien/ctrlp.vim
[+] [-] wahnfrieden|11 years ago|reply
[+] [-] swartkrans|11 years ago|reply
[+] [-] virtualwhys|11 years ago|reply
[1] https://github.com/szw/vim-ctrlspace [2] https://github.com/zhaocai/GoldenView.Vim
[+] [-] krick|11 years ago|reply
There's plugin for it in vim. Even several of them, as always. I don't remember which one I used and if it was completely ok, but I can find https://github.com/skammer/vim-css-color right away.
[+] [-] tuhdo|11 years ago|reply
[+] [-] statico|11 years ago|reply
[+] [-] snarfy|11 years ago|reply
https://github.com/OmniSharp/omnisharp-vim
[+] [-] TheDong|11 years ago|reply
[+] [-] krick|11 years ago|reply
Why? Well, there could be multiple answers, but essentially there's one main reason: it's just dead simple, while vundle and other ruby-inspired ones are not. Pretty much for the same reason I like pathogen+git thousand times more than emacs' package manager.
So even if it could be arguable that pathogen is better than vundle, there's completely no reason not to advise it.
[+] [-] 9diov|11 years ago|reply
The major feature is that it can install plugins in parallel. I've switched from vundle to it and have been quite happy.
[+] [-] eridius|11 years ago|reply
Also, I find MacVim to be a better experience than Vim in the terminal.
[+] [-] swartkrans|11 years ago|reply
[+] [-] bwilliams|11 years ago|reply
iTerm lets you do this, but Terminal.app doesn't.
[+] [-] ChristianBundy|11 years ago|reply
[+] [-] to3m|11 years ago|reply
[+] [-] function_seven|11 years ago|reply
[+] [-] gfodor|11 years ago|reply
[+] [-] Gonzih|11 years ago|reply