Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Ultimate Vim Distribution

vim.spf13.com

Post reply on HN
Print view View original

41–50 of 90 posts

Re: The Ultimate Vim Distribution

#41

Post by FuzzyDunlop »

exogen wrote: post #11

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. It actually made Vim worse , 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…

I agree with the sentiment, and it's exactly why I switched from a ready made emacs setup to a custom-rolled config.

Most of the stuff bundled in it isn't really necessary, and just makes it harder to understand the clean environment if you're new to it.

Even though it's more work, it's nice to know exactly how you're configuring your own environment, and you get to learn more about it as you do configure it.

To that extent I'm not even a fan of emacs' new package manager.

Re: The Ultimate Vim Distribution

#42

Post by bti »

njharman wrote: post #30
jlgreco wrote: post #3

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. 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…

This. Vim is vim is popular because it is a highly configurable tool that each user can tweak to be just right. But, 1) things like this will get new people using vim. Without usage, code rots. 2) things like this teach me all sorts of vim I did not know. In re 2: I really want to see their vimrc file without having to install this.

re 2: Up on GitHub

https://github.com/spf13/spf13-vim

Re: The Ultimate Vim Distribution

#43

Post by akurilin »

DiabloD3 wrote: post #14

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. https://github.com/Diablo-D3/dot_vim

I prefer vundle to pathogen, it's really brainless to use.

Re: The Ultimate Vim Distribution

#44

Post by erydo »

njharman wrote: post #35

> curl http://j.mp/spf13-vim3 -L -o - | sh I'm stunned that anyone would pipe from internet to shell. No SSL and redirecting just make it easier for the bad guy. It makes me angry that people are promoting this as an install method. Like suggesting your first name as a good password.

Ignoring the SSL bit, from a security standpoint is piping to the shell really any different than saying "run this installer application"? Either way you're allowing the source to run arbitrary commands on your computer.

Re: The Ultimate Vim Distribution

#46

Post by wahnfrieden »

owenjones wrote: post #39
wahnfrieden wrote: post #15

Earlier quoted context omitted.

Vundle is strictly better unless you automate your software updates and want to be able to update your vim plugins without having to launch vim to do so. Pretty tenuous but maybe some sysadmin-inclined people really prefer this.

You can update your bundles straight from the command line with: vim +BundleInstall! +qall Vim still opens but could be useful if you're trying to automate vim somehow.

Yeah. I'm just citing the only reason I've heard, which is that invoking vim just to update a plugin is gross. Which is kinda true - what happens if your vim config is in some bad state and doesn't start properly, your update process breaks unnecessarily (odd coupling to have). Definitely edge case-y, but a tradeoff anyway.

Re: The Ultimate Vim Distribution

#47

Post by wonderzombie »

jlgreco wrote: post #3

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. 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…

For my part, I used Vim for maybe a decade before switching to SublimeText 2 approx. four to six months ago. It was pretty close to impossible for me to get all the plugins and functionality I wanted set up correctly in Vim. Conversely ST2 ships with everything I want and with approximately zero config, so I jumped on it.

I don't have much intention of going back, but it's still useful to have an editor I can run in a terminal, so I installed UVD. We'll see how it goes, but I like the idea of a curated setup where I just drop in my custom crap from my old vimrc and call it good.

That said, I agree with the larger point that it's hard to see whether it will take off. But if it's easy for them to maintain it and they're scratching their own itch, it seems like a net win.

Re: The Ultimate Vim Distribution

#48

Post by qznc »

DiabloD3 wrote: post #14

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. https://github.com/Diablo-D3/dot_vim

Thanks for suggesting rooter. Did not know that.

Re: The Ultimate Vim Distribution

#49

Post by johncoltrane »

Symmetry wrote: post #6
jlgreco wrote: post #3

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. 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…

In term sof new stuff that's true, but there are a lot of things that modern plugins provide that obsolete the traditional way of doing things. For instance, people using EasyMotion never have to worry about counting how many words ahead they're moving and then typing c69w or whatever. And likewise, there are some things that everybody should have in their .vimrc, like incremental search, and it doesn't make sense to…

I tried it for a couple of weeks but I couldn't wrap my head around EasyMotion. `set incsearch` and `/foo` are all I need.

Re: The Ultimate Vim Distribution

#50

Post by dredmorbius »

erydo wrote: post #44
njharman wrote: post #35

> curl http://j.mp/spf13-vim3 -L -o - | sh I'm stunned that anyone would pipe from internet to shell. No SSL and redirecting just make it easier for the bad guy. It makes me angry that people are promoting this as an install method. Like suggesting your first name as a good password.

Ignoring the SSL bit, from a security standpoint is piping to the shell really any different than saying "run this installer application"? Either way you're allowing the source to run arbitrary commands on your computer.

Yes.

For me to trust an installer, implicitly, it's best for it to be part of my software distribution's package management system.

This means that the package is signed and checksummed, it's included in the distro's bugtracking system, and is being downloaded from a known set of mirrors.

Your next best option is to provide a download, checksums, and signatures, with a well-signed PGP/GPG key. At this point I can at least verify that the content is what you claim it is (whether or not that's something I plan on running is quite another matter).

Even a git repo provides a SHA1 checksum of a given commit that I can reference.

By recommending I curl-pipe-bash something, you're sending me a FLAGRANT signal that your security practices are somewhere well north of batshit crazy.

I ran into this while evaluating RVM (Ruby enVironment Manager), which itself turned out to be a requirement (or at least facilitator) for properly using Ruby for, of all things, supporting a Chef (configuration management tool) infrastructure. So ... in order to get a better handle on our server infrastructure ... the recommended and default practice is to install crap via curl-pipe-bash.

That cost us about six weeks of going through the damned installer and its effects (documentation is really poor) with a very fine-toothed comb. And I'm still not happy using it.

Post reply on HN