11–20 of 145 posts
Unfortunate that they don't mention licensing at all. (EDIT: Whoops, I'm completely wrong. Sorry. Move along, nothing to see here.) Since they use Git submodules, some licensing is inherited from packages like Command-T and vim-fugitive... but they wrote code themselves as well, so there's also that.
not a cool question but ... I wonder if it will install on windows without problems
It won't, it's mac os x only from the looks of it, which is kinda silly.
Getting started with plugins enabled makes it hard to understand where vim stops and plugins begin and make switching to a different (someone else's) vim setup confusing at best.
It also tends to feed the 'make it work like the last editor I used' syndrome, which is completely counter-productive.
Otherwise, nice work and good job open-sourcing it!
This is cool but it seems silly to have the default install method to be using "rake", I love vim but keep Ruby off most of my systems, what happened to good ol' fashion shell scripts.
Why is it silly? It's specific for OS X and OS X users already have ruby installed.
Emphasis on "for them".
I'm not saying you shouldn't share your setup. I wouldn't have learned vim (or screen back in the day, or pine, or many others) if I didn't crib from the dotfiles of those before me.
But at some point, your setup becomes so customized to you that you're the only one it works for. And that's why vim and emacs, ancient editors, still exist -- they're stable and can be modernized and tailored to the user over time.
This writeup (not mine) I completely agree with: http://mislav.uniqpath.com/2011/12/vim-revisited/
Earlier quoted context omitted.
It won't, it's mac os x only from the looks of it, which is kinda silly.
Not really, since it's developed by them and for them (a mac house). He seems pretty welcoming of your additions to make this Linux/Windows if you desire... but why on earth one would expect that THEY would have taken the time to make this multi-platform when they don't use it that way is honestly beyond me (i.e. silly).
Not to rain on anybody's parade here, but for first-time vim users I recommend not using any plugins and only selectively adding them one at a time after the basics (buffers, navigation, some ex mode, etc) are at least somewhat familiar. Getting started with plugins enabled makes it hard to understand where vim stops and plugins begin and make switching to a different (someone else's) vim setup confusing at best. It…
Please make sure you have the correct access rights and the repository exists.
Not to rain on anybody's parade here, but for first-time vim users I recommend not using any plugins and only selectively adding them one at a time after the basics (buffers, navigation, some ex mode, etc) are at least somewhat familiar. Getting started with plugins enabled makes it hard to understand where vim stops and plugins begin and make switching to a different (someone else's) vim setup confusing at best. It…