21–30 of 145 posts
Earlier quoted context omitted.
Why is it silly? It's specific for OS X and OS X users already have ruby installed.
Because everybody has at some point tried to run rake on a new project and found some version incompatibility along the depth of the abyss^Wstack.
Earlier quoted context omitted.
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).
Yes but VIM runs on everything, why make it Mac OS X specific when it's simplistic to make it "just use these vim files and it'll work on every computer"
That said, I started using vim with Janus and while it convinced me that vim could be a great modern editor, it left me too confused when I tried to make my own customizations. I ended up ditching it and hand-picking my own plugins. I suspect a completely new vim user would likely experience the same process with Maximum Awesome. Still, that doesn't mean these curated sets of plugins are a bad idea--if anything they can serve as a proof of concept for people who aren't yet convinced on the value of the editor.
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…
This said, I think these sort of dumps are great for experienced vim users who can pick through them and find individual fragments that they want to adopt.
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…
I know a few basic vim commands (switch modes, edit, write, quit) but have never used it to work on a complete project in a directory.
Great to see some love for tmux. Terminal vim + tmux is a lot more powerful than Gvim or MacVim. That said, I started using vim with Janus and while it convinced me that vim could be a great modern editor, it left me too confused when I tried to make my own customizations. I ended up ditching it and hand-picking my own plugins. I suspect a completely new vim user would likely experience the same process with Maximum…
I've picked up a few new tricks from their setup as well -- e.g. see the "Fix Cursor in TMUX" comment in vimrc.
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.
update: i like the empty line space indicators little boxes look cool