Farewell, Nano

Forever, I’ve used nano as my command-line text editor. I’ve never had an issue with it. In fact, it’s been so reliable that I’ve keep it around much longer than I should have. It still works well for most of my needs, but it’s time to expand my suite of skills and learn something new.

That’s why I’m switching to vim.

Out-of-the-box, vim is a tabula rasa, a blank slate, and it feels oddly empty. To fill this vacuum, my first step in making the transition was to explore plugin managers. Of course, this is following an introductory period to learn the basics. If I was going to successfully make the switch, I was going to need to first personalize my instance vim.

I selected Tim Pope’s pathogen.vim as my plugin manager. pathogen.vim allows for each plugin to be placed into its own version-controlled directory and loaded at runtime. Installing a plugin is straightforward: git clone into ~/.vim/bundle/. Simple, maintainable, elegant.

Here are a few of the plugins that comprise my base:

  • jellybeans.vim: Because everyone needs a cheerful, dark-mode enabled, color scheme.
  • nerdtree.vim: If you’re going to be using vim for any amount of time, you’ll want to have a file explorer.
  • fugitive.vim: A way more advanced git wrapper than I currently need, but a rich avenue for exploration and growth. I’m basically using this plugin to display git information in the 'statusline' via…
  • lightline.vim: In a nutshell, an easy to use and highly configurable 'statusline' plugin.

Feel free to take my initial configuration for a spin!

Library Systems Analyst

Focusing on cultural heritage institutions: discovery applications, data (and metadata) wrangling, web development, process automation, and system integration.