I have said it before here when people have discussed packaging up Vim stuff, and I stick by it: I really don't see this taking off.<p>Switching to using this does not appeal to me, an existing Vim user, and I think I am not an exception. If this does something new that I like I'll gladly throw that part into my setup, but there really isn't any reason at all that I can see for wanting to use this.<p>I don't think this is good for new Vim users either. If you are new to Vim there <i>already</i> is no shortage of things to learn (I think GVim steps up in this role nicely). Throwing more things into the mix isn't going to help a thing. And as you <i>(slowly)</i> pick up more and more of stock Vim, you are going to naturally build up your own setup. Before you know it you'll be at the same point that I think existing users are generally at.<p>This all said, I'm also a zsh user who cannot fathom why oh-my-zsh is popular...
> curl <a href="http://j.mp/spf13-vim3" rel="nofollow">http://j.mp/spf13-vim3</a> -L -o - | sh<p>I'm stunned that anyone would pipe from internet to shell. No SSL and redirecting just make it easier for the bad guy.<p>It makes me angry that people are promoting this as an install method. Like suggesting your first name as a good password.
I realize this is a different project, but since it looks similar: installing Janus was the worst decision I ever made while looking to improve my Vim experience.<p>It actually made Vim <i>worse</i>, sometimes by just slowing things down, other times because of the lack of quality control in the bundled plugins. One plugin actually caused data loss many times – it completely froze the editor when a certain syntax pattern was typed. All with just the default Janus settings.<p>To that effect, I hope quality control in spf13 is really, really good.
I don't get why this is loaded down with useless plugins... if you're using ctrlp/command-t, you don't need nerdtree. Vundle isn't as good as pathogen, neocomplcache isn't as good as supertab + clang_complete, and it lacks gundo, rooter, ultinips, and maybe other things.<p><a href="https://github.com/Diablo-D3/dot_vim" rel="nofollow">https://github.com/Diablo-D3/dot_vim</a>
Distributions like these are good for people who just need to <i>use</i> Vim, not necessarily for people who want to <i>learn</i> Vim. It's often better for people to add plugins and update their vimrc file as they learn Vim and figure out what their Vim style is.<p>This article helped me with my 2nd attempt to learn Vim: "Your first vimrc should be nearly empty" <a href="http://vimuniversity.com/samples/your-first-vimrc-should-be-nearly-empty" rel="nofollow">http://vimuniversity.com/samples/your-first-vimrc-should-be-...</a>
This seems very similar to Janus (<a href="https://github.com/carlhuda/janus" rel="nofollow">https://github.com/carlhuda/janus</a>). It has almost the exact same bundles and setup process.
I personally swear by <a href="https://github.com/scrooloose/vimfiles.git" rel="nofollow">https://github.com/scrooloose/vimfiles.git</a> installation. It doesn't go by some fancy name but does its work outstandingly. I have added to its vimrc wherever it deems fit.
ASK HN:
I am looking out for jumping out to a CSS selector in a css file from the HTML file I am editing for quite sometime in one key. Please see if you can guide me on this.
Yet another set nocompatible. In "The Ultimate Vim Distribution", no less.<p>I can't understand why <i>anybody</i> would want to use that kind of "distribution". All the vimrc tweaking and plugin dance is actually very beneficial in the first few months because it forces beginners to learn a lot of basics and, above all, how to use the help. And, well… experienced users already have a vimrc tweaked to hell and their own set of plugins.
I think this is fantastic. For beginners and not so much beginners, it is a great way to start with a very complete system for developing and build on/customize it the way you like. You don't lose any customization power as others have said. I just renamed my .vimrc to .vimrc.local and that's all, everything is working plus I earned a lot of extra-plugins that I didn't even know about.<p>I love it, thanks to the autor/s
Installed it, but now I'm getting this error when starting vim:<p>> E117: Unknown function: fugitive#statusline<p>> E15: Invalid expression: fugitive#statusline()
I think it is good for showing some different plugins and configuration options available in Vim. I think I will use the the included .vimrc file and plugins to look at to get ideas for my own .vimrc. The default in the distribution makes my Vim look like a christmas tree, which I don't really like.
the problem with packs... there is so much stuff to ingest, most of the stuff goes unused.<p>learn to use default vim first. then start adding aliases and macros as need to speed up things.<p>most of the plugins mentioned are useless to me. default vim is super powerful as it is.<p>why try to fix problems that aren't there? the beauty of vim is the unique way each user approaches it. every time i sit next to a vimmer i'm like 'how the hell did you do that!" same thing that happens when vimmers watch me code. ive been using vim for 6+ years now, i still haven't even got close to using 10% of it, and i daily use around 50 or so key commands.
I just installed this last night. I'm comparing it with <a href="https://github.com/fisadev/fisa-vim-config" rel="nofollow">https://github.com/fisadev/fisa-vim-config</a><p>Right now, fisa is slightly ahead because it is a bit faster.
I never really had a problem with configuring vim and installing plugins manually. This seems like it'll make vim more daunting for new users, while getting in the way of experienced users.
I dont like how the current line is always 0 and not the actual line number. How do I fix that? I have never seen this elsewhere.<p>I must admit that this distro will help my workflow.