vim
Get flash to fully experience Pearltrees
Vim anti-patterns | Arabesque
The benefits of getting to grips with Vim are immense in terms of editing speed and maintaining your “flow” when you’re on a roll, whether writing code, poetry, or prose, but because the learning curve is so steep for a text editor, it’s very easy to retain habits from your time learning the editor that stick with you well into mastery. Because Vim makes you so fast and fluent, it’s especially hard to root these out because you might not even notice them, but it’s worth it. Here I’ll list some of the more common ones. Moving one line at a time If you have to move more than a couple of lines, moving one line at a time by holding down j or k is inefficient.
The VI Gang Sign by Jon Beltran de Heredia, May 16th, 2007 Yes, even if you can't believe it, there are a lot fans of the 30-years-old vi editor (or its more recent, just-15-years-old, best clone & great improvement, vim ). No, they are not dinosaurs who don't want to catch up with the times - the community of vi users just keeps growing: myself, I only got started 2 years ago (after over 10 years of being a professional programmer). Friends of mine are converting today.
Why, oh WHY, do those #?@! nutheads use vi?
I’ve had an off/on relationship with Vim for the past many years. Before, I never felt like we understood each other properly. I felt that the kind of programming I’m doing is not easily done without plugins and some essential settings in .vimrc , but fiddling with all the knobs and installing all the plugins that I thought I needed was a process that in the end stretched out from few hours to weeks, months even; and it the end it just caused frustration instead of making me a happier coder. Recently, I decided to give Vim another shot.
Vim: revisited
How I boosted my Vim » nvie.com - Vimperator
http://nvie.com/posts/how-i-boosted-my-vim/ Published: September 14, 2010 Last updated: September 23, 2010 (highlight updates) Last updated: September 23, 2010 A few weeks ago, I felt inspired by articles from Jeff Kreeftmeijer and Armin Ronacher . I took some time to configure and fine-tune my Vim environment.
Update: Version 2.0 is up! There are now 4 versions to chose from: (If you are wondering what the differences are between the screen and print: the screen has less color variations, and no gradients to make it easier to read.) One designed for on-screen reading: PDF ( Excel 2011 source ), One designed for hard-copy reading: PDF ( Excel 2011 source ), One designed for monochrome printing: PDF ( Excel 2011 source ), and One designed for Red/Green color bindness -- a "Blue" theme PDF ( Excel 2011 source ). The color coded Legend / Keys helps provide guidance for your experience level. Green = Essential Yellow = Basic Orange / Blue = Advanced Red = Expert
Vim Cheat Sheat for Programmers by Michael Pohoreski
Coming Home to Vim
I’m a programmer. I work with text files for 6-12 hours every weekday so I care about the text editor I use. If switching to a different editor can increase my efficiency by even 10% it would save a good chunk of my time and let me get back to making cool things.
More than a year ago, I wrote about switching to Vim . I was quite happy with how it all worked, but I found myself switching back to Textmate after a while. I read through a lot of dotfiles to “steal” some configuration options from others, took some time to go through vimtutor , read some blogposts and after a while, I was quite happy with how it all worked. My new, full screen Janus-powered MacVim editor, with sexy drawer
Vim is hard, I just want to click around
A while ago I wrote a post about switching back to Vim . Since then I’ve written two plugins for Vim, one of which has been officially “released”. post : http://stevelosh.com/blog/2010/09/coming-home-to-vim/ Vim : http://www.vim.org/ A couple of people have asked me if I’d write a guide to creating Vim plugins. I don’t feel confident enough to write an official “guide”, but I do have some advice for Vim plugin authors that might be useful.
Writing Vim Plugins
mkdir ~/bin cp vimpager ~/bin chmod +x ~/bin/vimpager # put these in your ~/.bashrc or ~/.zshrc export PAGER=~/bin/vimpager alias less=$PAGER alias zless=$PAGER To use a different vimrc with vimpager, put your settings into a ~/.vimpagerrc or a file pointed to by the VIMPAGER_RC environment variable. You can also have a global config file for all users in /etc/vimpagerrc, users can override it by creating a ~/.vimpagerrc.
pager - Use ViM as PAGER
extradite.vim is a wrapper around git log -- [file] . I wanted tight integration between tig and vim, but there was no good way to do it. So I've replicated some of tig's functionality within vim instead.