Bloody VIM

Vim is a highly configurable text editor built to make creating and changing any kind of text very efficient. It is included as “vi” with most UNIX systems and with Apple OS X.

vim.org

You will encounter vi/vim as the incomprehensible text editor that pops up by default when you need to edit something in your sysadmin journey. Perhaps you issued the command to edit your Ansible vault, perhaps you forgot to add a message to a commit. It’s going to be unavoidable.

Here is the minimum knowledge you need to survive these encounters.

  • It has modes. When it opens up, you are in ‘moving around mode’. Use the cursor keys to get to where you need to.
  • When you actually want to edit something, press i now you’re in INSERT mode and it’s behaving how 99% of the world expect an editor to behave. When you type things, they go into the document where the cursor is.
  • When you are done, press escape to get out of INSERT mode, then these keys one at a time : w q

The underlying theory of Vim – that you spend more time moving around in text than editing it, is true of most sysadmin and programming tasks. So Vim has powerful, non-intuitive commands to do that efficiently. It’s impressive to watch people who have learned these arcane ways move around a file. They don’t have girlfriends. There are also powerful, non-intuitive commands for editing.

One response to “Bloody VIM”

  1. Use VS Code to work on remote files – dev.endevour Avatar

    […] or some code to work on, and it’s on a VM somewhere, you can always ssh in and use nano or vim to make your edits. Like a caveman. With an archaic editor, no intellisense, and no spell […]

    Like

Leave a comment