When I first started this blog, I was surprised (and disappointed) that Google’s Blogger platform didn’t have some nice built-in feature for code formatting and syntax highlighting. I experimented with a number of third-party solutions, but didn’t find anything that I particularly liked, so my posts have had some ugly-looking code in them. Until now.
To start off my reinvigorated vim education, I looked into why I get a helpful info bar when I have :split windows, but not when I am looking at a single file. The bar is called the statusline (:help status-line)
I use vim daily for my routine development work, and I get along fine with it. When I first got into it, I scrambled up the steep learning curve until I got to a plateau where I could be productive, and haven’t given it much thought since then. I can do all the basic stuff (and a few cool tricks), but other than that my editor is pretty low on the list of things I want to devote thought to.
My position changed, however, when a coworker recently decided to jump on the vim bandwagon.