I like PulseCursorLine, but I wonder why only on N and n? (e.g. not on *)
Steve Losh's .vimrc
51–60 of 103 posts
Re: Steve Losh's .vimrc
#52Here's a commented version of my .vimrc, which is modeled after Steve's, albeit nowhere near as comprehensive. (Looks like I lost it's fixed width in the paste? Sorry!) http://pastebin.com/jJQFxQpR For me it's a lot quicker to reference comments than the :help entry for each option. Thought it might help others who are creating/modifying their .vimrc. And of course, thanks Steve for continuing to share your stuff. I'…
Here is the code in a more readable gist without fixed width:
Re: Steve Losh's .vimrc
#53Anyone who knows who sjl is could have easily found his vimrc through his website. According to the bitbucket history, the file has been hosted there since at least 2009.
Re: Steve Losh's .vimrc
#54vimscript really is an abomination. vim users of the world unite! and create a proper macro language for your editor. and no: running an external python/ruby/brainfuck process does not count.
Re: Steve Losh's .vimrc
#55If you want to learn how to do this yourself, let Steve know here: http://leanpub.com/learnvimscriptthehardway
Re: Steve Losh's .vimrc
#56vimscript really is an abomination. vim users of the world unite! and create a proper macro language for your editor. and no: running an external python/ruby/brainfuck process does not count.
I dunno, I think the Python interface is adequate. Not great, but gets the job done. I write almost all my Vim scripts in Python.
Re: Steve Losh's .vimrc
#57I also have a huge vim configuration:
https://github.com/sashahart/.vim
I highly recommend putting your vim configuration on github or similar, you don't have to worry about losing your config and it gets easier for everyone to learn the new tricks
Re: Steve Losh's .vimrc
#58Earlier quoted context omitted.
Actually I'm planning on splicing it into MakeGreen, so instead of getting a green bar when my tests pass I get Nyan Cat flying across my window. Maybe over Thanksgiving weekend I'll get around to it. Edit: Also, if anyone can show me how to draw an ASCII-art Nyan Cat in one line of text that would be awesome. Nothing I tried looked recognizable.
how bout 2 lines? http://jsfiddle.net/MHj9N/
Ascii Nyan cat!! Thank-you! My mind just melted.
Re: Steve Losh's .vimrc
#59vimscript really is an abomination. vim users of the world unite! and create a proper macro language for your editor. and no: running an external python/ruby/brainfuck process does not count.
I dunno, I think the Python interface is adequate. Not great, but gets the job done. I write almost all my Vim scripts in Python.
Using Python and other runtimes is often kind of slow - it's not a huge deal but if you have a lot of this stuff in your config, then vim might start up only like 8 times faster than Eclipse.
The other thing is that the Vim API you use in these other languages is pretty much Vimscript anyway.
For me, Vimscript is basically a normal imperative language in the general neighborhood of perl and shell... I agree it is more awkward to write than Python, particularly with escaping. But it's a decent DSL for configuring text editors, and Python isn't as much.
Re: Steve Losh's .vimrc
#60Does this affect performance in any way? 1k+ lines is quite a lot.
vimrc affects startup time, but like any program it isn't the lines but the work done which will make it slow or fast. How slowly does your computer read a 1000-line text file? vim is fast, setting some parameters in vimrc doesn't change that. Avoiding configuration that will make your life easier out of fears about performance is premature optimization.
If you have a ton of autocmds for frequent events, things can slow down. I also find that things can get slow when LOTS of calls are made to a language other than Vimscript.
But fundamentally, run Eclipse and Netbeans and gedit and emacs - vim should compare favorably even with a ton of config.
If you want to actually profile your startup time, try this on a recent version of vim: vim --startuptime=vim.log