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

61–70 of 90 posts

Re: The Ultimate Vim Distribution

#61

Post by papaver »

the problem with packs... there is so much stuff to ingest, most of the stuff goes unused.

learn to use default vim first. then start adding aliases and macros as need to speed up things.

most of the plugins mentioned are useless to me. default vim is super powerful as it is.

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.

Re: The Ultimate Vim Distribution

#62

Post by ZephyrP »

dredmorbius wrote: post #50
erydo wrote: post #44

Earlier quoted context omitted.

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…

http://seclists.org/fulldisclosure/2006/Mar/130

Just some food for thought concerning package ecosystems.

Re: The Ultimate Vim Distribution

#63

Post by arkenflame »

vessenes wrote: post #40
spf13 wrote: post #24

Earlier quoted context omitted.

This is my project. I was surprised to see it on HN today. It has a lot in common with Janus on the surface. IMO Janus is also a good project. Where it differs is spf13-vim is focused on cross platform dependency, keeping with vanilla vim feel and having no external dependencies (with the exception of git). My understanding on Janus is that it focuses on Ruby (spf13-vim supports Ruby well, but Python, JavaScript, PHP…

Thanks for spf13 -- I use it every day, on Mac and Linux, with Python. I do have one persistent, annoying problem with it, though, since I've got you here -- inserting close braces/parens OFTEN doesn't work with whatever plugin you use for the auto-closing. How do I turn it off? I remember trying to get rid of it, and failing miserably.

I also use this daily, and have the same problem. I suppose this speaks to the weakness others have expressed (in using a premade configuration setup vs. slowly rolling your own), but I have otherwise found spf13-vim very useful.

Re: The Ultimate Vim Distribution

#64

Post by nvmc »

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.

Re: The Ultimate Vim Distribution

#65

Post by lowboy »

dredmorbius wrote: post #57
erydo wrote: post #54

Earlier quoted context omitted.

First: I'm not recommending anything—I'm asking a question. This isn't my practice but it's important to play devil's advocate sometimes. Second, the question was not whether piping to shell is a good way of doing installations. The question was whether it's actually worse than the common method of offering up an untrusted downloadable executable. Many (or most) consumer software downloads that you'll find for Mac or…

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

Re: The Ultimate Vim Distribution

#66

Post by TheGateKeeper »

dredmorbius wrote: post #57
erydo wrote: post #54

Earlier quoted context omitted.

First: I'm not recommending anything—I'm asking a question. This isn't my practice but it's important to play devil's advocate sometimes. Second, the question was not whether piping to shell is a good way of doing installations. The question was whether it's actually worse than the common method of offering up an untrusted downloadable executable. Many (or most) consumer software downloads that you'll find for Mac or…

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…

If someone is actively trying to be a mitm and injecting things into your connection - you have far far worse problems than corrupted software.

Re: The Ultimate Vim Distribution

#67

Post by [deleted] »

sigzero wrote: post #59
olalonde wrote: post #13

Earlier quoted context omitted.

I think you are an exception. I can't get anything done with vanilla Vim (no smart indentation for instance) and install Janus anytime I need to use Vim on a new shell.

A couple of lines in your .vimrc and boom you have that and more.

[deleted]

Re: The Ultimate Vim Distribution

#68

Post by olalonde »

sigzero wrote: post #59
olalonde wrote: post #13

Earlier quoted context omitted.

I think you are an exception. I can't get anything done with vanilla Vim (no smart indentation for instance) and install Janus anytime I need to use Vim on a new shell.

A couple of lines in your .vimrc and boom you have that and more.

... or one bash command to install Janus.

Re: The Ultimate Vim Distribution

#70

Post by xyzzyb »

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 switched to vundle from pathogen and I'm much happier for it.

They're both great, but pathogen requires that you setup the plugin directories yourself which makes keeping the plugins updated a pain since you either set them up as their own git repos (which you have to remember to update) or git submodules if you're trying to maintain a repo of your entire configuration.

Vundle just requires a few lines in your config and is already git/github aware and just does the right thing. It's also trivial to see at a glance what I've installed.

Uninstalling a plugin from vundle is as easy as removing the line in the config and telling vundle to update.

https://github.com/sdball/dotfiles/blob/master/vim/vimrc

Post reply on HN