I'm using this one which is much better
http://github.com/humiaozuzu/dot-vimrc
The Ultimate Vim Distribution
71–80 of 90 posts
Re: The Ultimate Vim Distribution
#72Ctrlp link is broken - use this: https://github.com/kien/ctrlp.vim
Re: The Ultimate Vim Distribution
#73I 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.
I love it, thanks to the autor/s
Re: The Ultimate Vim Distribution
#74I 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. 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. I don't think this i…
Sort of related: I only use Emacs today because of the Emacs starter kit.
Maybe it's particular to Emacs, but I've found that the defaults are often terrible, and half of all tutorials I see for _anything_ are about changing the default case.
Re: The Ultimate Vim Distribution
#75Earlier quoted context omitted.
I'll check that out, thanks. My zsh setup has been pretty stagnant for a while now, probably about time I gave it some love.
In case it isn't clear, prezto is a fork of oh-my-zsh which has basically been rewritten bit by bit to make everything much cleaner and saner. I highly recommend it. The history-substring-search and syntax-highlighting modules are brilliant. You will be the envy of all your friends and neighbours.
I've been using oh-my-zsh and the startup is really slow. I hear prezto solves this. How do i upgrade from oh-my to prezto? No one seems to answer that ?
Re: The Ultimate Vim Distribution
#76I personally swear by https://github.com/scrooloose/vimfiles.git 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.
Re: The Ultimate Vim Distribution
#77I personally swear by https://github.com/scrooloose/vimfiles.git 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.
Is Martin Grenfell scrooloose the author of NERD and syntastic, or just copied them onto github?
Re: The Ultimate Vim Distribution
#78Earlier quoted context omitted.
How is vundle worse?
I dunno, I had problems trying to make it do something, but I forget what. I almost want to say it was git submodule related, but it was like a year or more ago.
So then why the hell did you say Pathogen was better than Vundle? Vundle is Pathogen + crack.
People should think about what they say.
Re: The Ultimate Vim Distribution
#79Earlier quoted context omitted.
At the very least, pipe-to-shell means you're left without an audit trail, if you're actually practicing that method. With a downloadable executable or installer, I'm left with a file that I can save, checksum, scan for vulnerabilities, and/or refer to at a later date should I find that there are concerns I didn't discover initially. curl-pipe-bash, especially in the absence of SSL/TLS, leaves me vulnerable to inject…
While I agree 100% with your advice for mission-critical servers, for a dev machine I don't see the problem with the ease of curl -> sh. It takes "very very very bad idea" down to "you probably should at least check out the installer script first".
Where do you think that code for mission-critical servers gets developed?
There's a pretty scary amount of iffy public code that ends up on mission-critical servers. I could outline some chains of connection, but briefly: it's very easy for someone's cheesy little website to become a significant player in another organization's processing.
That "website" you're going to likely runs not only on multiple servers, but in multiple datacenters across multiple organizational borders: core site, sales, support, order fulfillment, marketing analytics, web analytics, email, messaging, social integration ....
The best way not to get into bad habits on your production, mission-critical systems is to not allow them anywhere else.
Granted, this is a Vim suite, but I'm seeing similar brain death in far too many corners.
Re: The Ultimate Vim Distribution
#80I 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. 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. I don't think this i…
I download oh-my-zsh(or the fork Prezto), pick a theme, tweak 1-3 settings, load my custom PATH, and I'm in excellent shape. I have a shell that works great with little work.