ad477bf7ad4e

Introduce nunmap and prevent surprising behavior.

Thanks to @sedm0784 on GitHub for pointing it out.
[view raw] [browse files]
author Steve Losh <steve@stevelosh.com>
date Fri, 12 Oct 2012 19:42:20 -0400
parents d4af69670336
children 7d5493505f04
branches/tags (none)
files chapters/05.markdown

Changes

--- a/chapters/05.markdown	Fri Oct 12 19:35:14 2012 -0400
+++ b/chapters/05.markdown	Fri Oct 12 19:42:20 2012 -0400
@@ -20,7 +20,12 @@
 
 When you map keys with these commands Vim will take *other* mappings into
 account.  This may sound like a good thing at first but in reality it's pure,
-unadulterated evil.  Let's talk about why.
+unadulterated evil.  Let's talk about why, but first remove those mappings by
+running the following commands:
+
+    :::vim
+    :nunmap -
+    :nunmap \
 
 Recursion
 ---------
@@ -56,7 +61,11 @@
         * `dd` is mapped, so perform the mapping.
             * ...
 
-This mapping can never finish running!
+This mapping can never finish running!  Go ahead and remove it with the
+following command:
+
+    :::vim
+    :nunmap dd
 
 Side Effects
 ------------
@@ -111,3 +120,5 @@
 
 Convert all the mappings you added to your `~/.vimrc` file in the previous
 chapters to their nonrecursive counterparts.
+
+Read `:help unmap`.