NEXT STEPS

Learning Vim

Appendix A — Going Further

What You Have Covered

This course has taken you from opening a file for the very first time all the way through marks, registers, diff mode, configuration, and shell integration. That is a solid foundation — you now have the mental model that most long-term Vim users rely on every day.

  • Chapter 1Introduction— modal editing, installation, first steps
  • Chapter 2Basics— the five modes, file operations, quit variants
  • Chapter 3Moving Around— HJKL, word and line motions, search
  • Chapter 4Changing Text— operators, yank/put, registers, substitution
  • Chapter 5Marks— local and global marks, the jump list
  • Chapter 6Buffers, Windows and Tabs— splits, vimdiff, reading files
  • Chapter 7Configuration— .vimrc, mappings, abbreviations, custom commands
  • Chapter 8Day to Day Vim— startup flags, diff mode, archive editing, shell filters
The most important thing to do next: keep using it. The hardest part of Vim is not learning the commands — it is building the muscle memory. Commit to using Vim for real work for two weeks without switching back to a comfort-zone editor, and most of it will become automatic.

Built-in Resources You Already Have

:help — the manual that ships with Vim

Vim's built-in help is one of the best pieces of documentation packaged with any open-source tool. It is comprehensive, searchable, and always matches the exact version you are running.

:help              # open the help index
:help {topic}      # search for a specific topic
:help user-manual  # the full narrative user manual (excellent reading)
:help quickref     # a compact quick-reference of all commands
:help tips         # collection of Vim tips from the developers

Inside help: Ctrl+] follows any hyperlink (shown in |pipes|), Ctrl+O goes back. Close with :q.

vimtutor — the interactive tutorial

If you have not run vimtutor yet, do it now. It is a 30-minute hands-on walkthrough that ships with every Vim installation. Unlike reading docs, it teaches you by having you actually edit a file.

vimtutor           # run from your terminal — it opens a practice file

The tutorial covers the basics thoroughly and is worth revisiting periodically — you will notice things you missed the first time.

Official Documentation Online

Cheat Sheets and Quick References

A good cheat sheet on your desk or a second monitor is genuinely useful during the first few months. Here are the best ones available — all free, most printable.

🗂️
Widely considered the definitive Vim cheat sheet. Clean layout, covers all modes, motion commands, operators, and more. Available in multiple languages. Print-friendly. This is the one to bookmark.
🗂️
A well-organised, colour-coded reference card from the devhints collection. Slightly more condensed than rtorr — good for printing on a single page.
🗂️
A focused, no-frills one-page reference. Particularly good for beginners — it prioritises the commands you will actually use rather than listing every single option.
🗂️
A compact two-column PDF designed specifically for printing. Covers motion, editing, search, and Ex commands on a single sheet of paper. By Michael Goerz.
🗂️
A keyboard-diagram style reference showing key positions visually. Very useful for understanding the spatial logic of Vim's layout — why the commands are where they are.

Learning Resources

Free Books and Long Reads

Going Beyond Vim: Plugins

Stock Vim is already very capable, but the plugin ecosystem takes it much further. Once you are comfortable with the basics, a small set of well-chosen plugins can close the gap between Vim and a full IDE — while keeping the speed and keyboard-driven workflow that makes Vim worth using in the first place.

Plugin managers

Install a plugin manager first. It handles downloading, updating, and removing plugins through your .vimrc.

ManagerBest forLink
vim-plugMost users — simple, fast, minimal configgithub.com/junegunn/vim-plug
VundleClassic option, well documentedgithub.com/VundleVim/Vundle.vim
lazy.nvimNeovim users — modern, fast-loadinggithub.com/folke/lazy.nvim

Plugins worth knowing about

PluginWhat it does
NERDTreeFile explorer sidebar — browse and open files with a tree view
fzf.vimFuzzy file finder — open any file by typing part of its name
vim-fugitiveGit integration — run git commands, browse diffs, blame, all inside Vim
vim-airlineEnhanced status line showing mode, git branch, file info
ALEAsynchronous linting — real-time syntax warnings as you type
coc.nvimLanguage Server Protocol (LSP) — autocomplete, type hints, go-to-definition
vim-surroundAdd, change, or remove surrounding quotes/brackets/tags with a few keys
vim-commentaryToggle comments on any line or selection with gcc
vim-gitgutterShows git diff markers (+/−/~) in the sign column as you edit
gruvboxOne of the most popular colour schemes — warm, retro, easy on the eyes
Start small with plugins. The temptation is to install twenty plugins on day one and turn Vim into a mini-IDE. The better path is to learn stock Vim thoroughly first (which you have now done), then add one or two plugins that solve a specific friction point. You will understand what each plugin is doing and why — and your config will stay fast and maintainable.

Should You Switch to Neovim?

Neovim is a fork of Vim started in 2014 with the goal of modernising the codebase. It is fully compatible with Vim — everything in this course works identically in Neovim — but it adds:

  • Built-in LSP (Language Server Protocol) support — autocomplete and diagnostics without plugins
  • Lua as a first-class configuration language (alongside Vimscript)
  • A more active plugin ecosystem with modern tooling
  • Better async performance for linting, completion, and search
  • Terminal emulator built in

If you are just starting out, do not worry about this. Learn Vim first — every skill transfers. If after a few months you find yourself wanting a richer plugin ecosystem or are doing heavy programming work, Neovim is a natural upgrade path. The official Neovim site has installation instructions and a migration guide.

A Note on Humour

No Vim appendix is complete without acknowledging the memes. Vim has a rich tradition of jokes — mostly about how to quit it (:q!, as you now know), the learning curve, and the eternal Vim vs. Emacs debate. If you want to explore the lighter side:

  • The Vim Beginners Site has a Vim Humour section worth a browse
  • Search "how do I exit Vim" on Stack Overflow — the question has over 4,000 upvotes and the answers have become something of a rite of passage
  • VimGolf is genuinely entertaining even when you cannot solve the puzzles — reading other people's solutions teaches you something new every time
The best way to get better at Vim is to stop switching back to another editor when things get difficult. Every time you reach for the mouse, ask: is there a Vim way to do this? Usually there is — and once you find it, you will not forget it.