small medium large xlarge

The latest version of the book is B3.0, released 16 days ago. If you've bought a PDF of the book and would like to upgrade it to this version (for free), visit your home page.

By default this page displays the errata for the latest version of the book. If you have a previous version, select it here:

If you've found a new error, please submit it.

  • Typo
  • Tech. error
  • Suggestion
  • Maybe next edition
  • Not a problem
  • Reported in: B2.0 (07-Jan-18)
PDF page: 6
"In Vim 8, you can have support for either Python 2 or Python 3. " Not strictly true. The Windows version supports dynamic loading of Python, and a...more...
  • Reported in: B3.0 (06-Feb-18)
PDF page: 13
Hi Drew, On page 13 you state that it is necessary to restart vim after installing a plugin. Apparently this is not really necessary. On stackexchang...more...
  • Reported in: B1.0 (17-Nov-17)
PDF page: 23

When I copy "git add ." it's paste "gitadd."--Nicolas Ledez

Drew Neil says: I suspect that this is a general issue with copy/pasting text from PDFs, rather than a specific issue with this book. I've been able to reproduce the issue that you describe, but I can't think of any way of fixing it. (The source text that the PDF is generated from certainly has spaces between "git" and "add" and the dot.) Perhaps I should address this in the introduction to the book by advising the reader to type out commands by hand (a la Zed Shaw in "Learn Python the hard way").
  • Reported in: B1.0 (17-Nov-17)
PDF page: 26

When I copy "find . -type f | wc -l" it's paste "find.-typef|wc-l"--Nicolas Ledez

  • Reported in: B1.0 (21-Nov-17)
PDF page: 51
Hello, In the "Using the location list" section: > If you already have muscle memory for using these built-in commands you’ll find them appealin...more...
Drew Neil says: Here's an example to illustrate: say you have a buffer open and you have entries in the location list at line 1, line 11, and line 21. You use :lfirst which puts your cursor on line 1. Then you use :lnext which puts your cursor on line 11. Then you move your cursor up a couple of lines, leaving it on line 8. Now if you use :lnext again, you jump to line 21 - there's a certain logic to that, but I always find it a little bit jarring. I expect to jump to the next entry after my cursor position, and that's exactly how the ale_next mappings works. I was hoping that I could get away without having to spell out the differences so explicitly (because it takes a lot of words to do it!). It looks like I will have to spell it out after all.
  • Reported in: B1.0 (02-Nov-17)
PDF page: 96
For session handling, I'd recommend `using xolox's vim-session plugin, xolox/vim-session. This plugin has the xolox/vim-misc plugin (which has some...more...