Wow. I wish I had this exact setup. I have never been good at configuring Vim and the SPF-13 VIM distro is wonky. Would save me from buying Sublime
Try using Vundle to add one plugin at a time!
Vim After 11 Years
171–180 of 254 posts
Re: Vim After 11 Years
#172The author mentioned CtrlP for fuzzy filename matching. Its great because it's in pure Vimscript, but in my experience it becomes unusably slow for moderately sized projects. A month or two ago, I switched back to CommandT (requires Vim to be compiled with Ruby support, engine written in C) and haven't thought twice about it since then.
I've been meaning to try out matcher[0] for usage with CtrlP, I'm not sure how well it works but it's written in C and is purported to speed up search. Not sure if it's still being maintained, however... [0] https://github.com/burke/matcher
It works quite well. The only negative I've found is that using matcher seems to disable CtrlP's usual highlighting of which letters in a search result are matched.
In the end, though, I went back to Command-T.
Re: Vim After 11 Years
#173Minor nitpick, but can any terminals do squiggly underlines or is that still a gVim only feature?
iTerm2, at least, can show underlines where you'd expect squiggly lines in GUI vim. It's not as nice as the squigglies but it's pretty functional in practice.
Re: Vim After 11 Years
#174The author mentioned CtrlP for fuzzy filename matching. Its great because it's in pure Vimscript, but in my experience it becomes unusably slow for moderately sized projects. A month or two ago, I switched back to CommandT (requires Vim to be compiled with Ruby support, engine written in C) and haven't thought twice about it since then.
You won't see the 'indexing' as much if you keep indexes between runs of vim:
let g:ctrlp_clear_cache_on_exit=0
Re: Vim After 11 Years
#175No Command-T!? FAIL.
Re: Vim After 11 Years
#176Every time I read an article like this, it's how a power user installs an array of plugins and customizations to really soup up Vim, which to me kind of misses the point. If you want that level whiz-bang, use Coda or Sublime Text 2 or Eclipse or whatever. I don't recall where I saw this, but someone advised disabling syntax coloring in your editor to remove a crutch (and, secondarily, to visually simplify your enviro…
"If you want that level whiz-bang, use Coda or Sublime Text 2 or Eclipse or whatever. I don't recall where I saw this, but someone advised disabling syntax coloring in your editor to remove a crutch (and, secondarily, to visually simplify your environment)." Perhaps you might enjoy using ed... From: patl@athena.mit.edu (Patrick J. LoPresti) Sender: news@athena.mit.edu (News system) Subject: The True Path (long) Date:…
I actually had to go look at the real man page to make sure.
Re: Vim After 11 Years
#177Every time I read an article like this, it's how a power user installs an array of plugins and customizations to really soup up Vim, which to me kind of misses the point. If you want that level whiz-bang, use Coda or Sublime Text 2 or Eclipse or whatever. I don't recall where I saw this, but someone advised disabling syntax coloring in your editor to remove a crutch (and, secondarily, to visually simplify your enviro…
someone advised disabling syntax coloring in your editor to remove a crutch (and, secondarily, to visually simplify your environment) ... You have to read the code more closely, and think more carefully about what's on screen
I don't want to have to think more carefully about things that don't matter like syntax. Highlighting gives you visual clues so you can get meaning from code more quickly and get on with it, instead of having to read everything carefully.
Plus: pretty colors.
Re: Vim After 11 Years
#178The author mentioned CtrlP for fuzzy filename matching. Its great because it's in pure Vimscript, but in my experience it becomes unusably slow for moderately sized projects. A month or two ago, I switched back to CommandT (requires Vim to be compiled with Ruby support, engine written in C) and haven't thought twice about it since then.
I have a repo with 3000+ files and I can't notice any delay searching with CtrlP. I have the following custom file listing command in my vimrc: let g:ctrlp_user_command = { \ 'types': { \ 1: ['.git/', 'cd %s && git ls-files'], \ 2: ['.hg/', 'hg --cwd %s locate -I .'], \ }, \ 'fallback': 'find %s -type f' \ }
Just made my CtrlP use ag[1], it's awesome now :-)
let g:ctrlp_user_command = 'ag --nogroup --nobreak --noheading --nocolor -g "" %s '
Re: Vim After 11 Years
#179Lots of people seem to declare ; or , to be useless keys and remap them. They're two of my most used movement keys in certain circumstances. I used to have , remapped to but switched back when I realised what I was missing out on. I'd advise anybody else to reconsider if they've made the same mistake I did.
On a related note, I think that f and t become ever more awesome if you use fanfingtastic: https://github.com/dahu/vim-fanfingtastic
Re: Vim After 11 Years
#180Earlier quoted context omitted.
> All of that can be done much more efficiently without the mouse: Surely we don't need to get into this sort of thing here. If you don't know how to do it without the mouse, then it's more efficient to do it with the mouse. If you don't remember how to do it without the mouse, then it's more efficient to do it with the mouse. If you just like using the mouse better, then …. Anyway, and perhaps more importantly, it d…
It doesn't hurt these "anyone" to be pointed at better ways to do what they do.
There is no "better", young padawan.