Hacker News Reader

Hacker News

Comment by IanCal | Hacker News Reader

Parent Full thread

IanCal

1) Dump Janus, add the plugins you actually want

2) True

3) :set paste

4) Then wrap it in a function

5) I've always found ctrl-p to be snappy actually. You can replace the matcher with ag or similar

> write the Vim configuration lines required to cause those files to be ignored. You have got to be kidding me.

Write a small amount of config once per project? It's no more complex than adding things to a UI

    set wildignore+=*/tmp/*,*.so,*.swp,*.zip

6) No, vim can't, but plugins can. Ctrl-p has this feature (http://superuser.com/questions/390011/fuzzy-find-within-file...)

7) Stop just navigating with j and k.

> After reading this list, feel free to tell me how I'm doing it wrong on twitter.

You're not googling anything to find out the answer?

Also, because occasionally people haven't heard of it, get Gundo. http://sjl.bitbucket.org/gundo.vim/

Vim has a full tree undo, gundo makes it easy to navigate and see diffs between changes in code.

View on HN

But that's kinda the problem with vim. Having a sane configuration takes hours of setup and googling.

Depending on how you define "sane" it can be months. Vim is said to be a programming language for text editing - I wouldn't expect anything less of a complexity from a thing like this. I recently learned Emacs and it took me two months - that short because I already went through the process with vim some years ago - to learn it and configure it to my liking. My Emacs config counts 983 lines with comments and whitespaces removed[1]. My .vimrc was shorter, but mainly because I dislike vimscript and like Lisps.

[1] cat .emacs.d/config/*.el | egrep -v '^$' | egrep -v '^;;' | wc -l

That's only the first time. It's a completely different paradigm and you have to learn it. Once you've learnt it this entire list is a non-issue. Not only that - configure it as you want, then take that config with you to every other machine that you ever use - surely that's worth the effort.

That's not the problem. The problem is some people's assumption that they can pick up Vim just like any other editor and use it right away.

It takes time to be productive with Vim. There's no way to get around that.

It starts with a sane configuration, the problem is when you want to add loads of features you have to spend a small amount of time adding them. The alternative is to have a fucking insane amount of functionality present to begin with because everyone wants something slightly different.

Re (3), no, :set paste does not fix his problem.

]p does, though.

That pastes with adjust indentation.

I've just re-read the problem, I thought he was talking about vim automatically indenting everything.

It should be reasonably easy to create a function for this though, prefix each line in the buffer with 'indent(".")' spaces, or copy the whitespace at the beginning of the current line.

IMO The only real problem with Vim is lack of proper auto-complete.

Reply on news.ycombinator.com