Hello guys,<p>I wanted to get your feedback on my recent project : it aims to unify Vim configuration by aggregating some common plugins in order to provide an easy-to-use « package ».<p>It's called vimified : https://github.com/zaiste/vimified<p>The idea was to make it simpler than Janus (e.g. vundle instead of submodules et al.); it is also somehow similar to spf13-vim.<p>What do you think? Thanks!
"The Ultimate Vim Configuration" is like saying "The Ultimate Pair of Pants." No matter how hard you try, one size just doesn't fit all.<p>That having been said, projects like this and Janus are definitely a step in the right direction.
I wish each plugin listed had a descriptive paragraph instead of just a one liner. I've meticulously curated my vimrc to accommodate my particular work-flow and visual preferences, so I'm pretty hesitant to introduce a bunch of new plugins and configurations without knowing exactly what is happening (as many of the plugins go unused if I am not distinctly aware that I wanted the functionality).
Thanks for the hard work, but the only person that should decide what is or not in my .vim folder and my .vimrc is me.<p>Also the name doesn't seem very good to me : "vimifying" something means that you make something (a browser, a PDF viewer, whatever that is "non-Vim-like") more "Vim-like". Customizing the hell out of Vim is quite the opposite.
I want a rewrite of vim's internals so that it can be scripted with something else than vimscript, which is, to this day, the only way to have access to all the bang vim has to offer. And that's pretty sad cause vimscript is not a very good language.
How is this better then <a href="https://github.com/astrails/dotvim" rel="nofollow">https://github.com/astrails/dotvim</a> ? :)<p>The readme is better and does not pretends to be ultimate, just a pretty good one ;)
Why should I choose vimified over spf13-vim? [Especially because I am on Windows and I don't see any details about Windows support.]<p>Also, why should I install plugins about languages which I don't care?
Vim completely freezes and consumes 100% cpu right after starting up.<p>Also, the yankring plugin has a problem with non-existant ~/.vim/tmp directory.