VIM Cheatsheet

THE PRACTICAL GUIDE · NORMANDIN SYSTEMS

Get more from VIM Cheatsheet

VIM Cheatsheet summarizes common Vim editing, navigation, search, and command-mode operations. Vim is modal: the same key can insert text in one mode and perform an action in another. Knowing the current mode and the modified state of the buffer is essential before adapting a shortcut from a reference. A cheatsheet works best as a memory aid while you practice a concrete task. Read the command or syntax together with its arguments, placeholders, and surrounding context. Similar-looking options can have very different meanings, and an example written for one platform or version may need adjustment elsewhere. Keep the reference beside a small test case, use read-only examples first when possible, and check the relevant help output before applying an unfamiliar command to valuable files or a running service.

Guide updated October 13, 2026

How to use this tool

1. Identify the operation you want to perform and find the matching section of the reference. Read the whole example before copying any part of it.
2. Open a disposable file, confirm the current mode, and practice the desired movement or edit before applying it to important text.
3. Review the example below and compare its expected behavior with a small sample of your own input before continuing.
4. Try the adapted example on a small test case, compare the result with the explanation, and save the command with a note about the context in which it works.

SEE IT IN PRACTICE

A worked example

In Normal mode, type :w and press Enter

Vim writes the current buffer to its associated file when permitted

The command-line operation saves the buffer; permissions, filename state, and prompts can affect the result.

Mode determines what a key means

In Insert mode a key may add text, while in Normal mode it may move, delete, or combine with another command. Ex command-line mode adds another interpretation layer. When learning a reference shortcut, first establish the mode and then watch the buffer change. A disposable file makes it easier to understand motion, operator, and count combinations without risking important content. Keep undo available and inspect the current filename and modified indicator before saving or quitting.

Mappings and buffers add context

User mappings and plugins can change familiar key behavior, and multiple buffers can contain unsaved changes even when only one is visible. A forced quit or overwrite should be a deliberate decision rather than a reflex copied from a cheatsheet. Review prompts and understand which buffer or window a command targets. After editing a structured configuration file, run the relevant syntax validation outside the editor. Saving a buffer successfully only establishes that text was written, not that the consuming application accepts it.

When this tool is useful

• Review Vim navigation commands
• Understand save and quit operations
• Practice modal editing on a small file

Tips for a better result

• Check mode, filename, modified status, and command prompts, and use undo deliberately when practicing edits.
• Replace example paths, identifiers, and names deliberately. Copying a reference command unchanged can target a different file, branch, service, or environment from the one you intended.
• Keep the source and the settings used for this result together. That makes a later comparison or correction easier, especially when another person needs to reproduce the same outcome.

Frequently asked questions