summaryrefslogtreecommitdiffstats
path: root/runtime/doc/undo.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2006-03-21 21:23:25 +0000
committerBram Moolenaar <Bram@vim.org>2006-03-21 21:23:25 +0000
commit76916e60ed6296aff1b855408b81cc08b8e07257 (patch)
treebfc4e296dfdec7e856eaabe81a4fdd32697130c5 /runtime/doc/undo.txt
parenteee697b748159dfc85f4dd9fe6478a31a1f9d145 (diff)
updated for version 7.0231
Diffstat (limited to 'runtime/doc/undo.txt')
-rw-r--r--runtime/doc/undo.txt13
1 files changed, 5 insertions, 8 deletions
diff --git a/runtime/doc/undo.txt b/runtime/doc/undo.txt
index e34d30d59b..4ff7e20ce5 100644
--- a/runtime/doc/undo.txt
+++ b/runtime/doc/undo.txt
@@ -1,4 +1,4 @@
-*undo.txt* For Vim version 7.0aa. Last change: 2006 Mar 16
+*undo.txt* For Vim version 7.0aa. Last change: 2006 Mar 21
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -108,10 +108,10 @@ change.
==============================================================================
4. Undo branches *undo-branches*
-Above we only discussed one line of undo. But it is also possible to branch
-off. This happens when you undo a few changes and then make a new change.
-The undone changes become a branch. You can go to that branch with the
-following commands.
+Above we only discussed one line of undo/redo. But it is also possible to
+branch off. This happens when you undo a few changes and then make a new
+change. The undone changes become a branch. You can go to that branch with
+the following commands.
What matters here is the order in which the changes are made. Undo and redo
are not considered changes in this context. After each change you have a new
@@ -179,9 +179,6 @@ Delete the second word by pressing "x" three times:
Now undo that by using "g-" three times:
one o three ~
one wo three ~
- one two three ~
-
-Continue going back in time by pressing "g-" one more time:
two three ~
You are now back in the first undo branch, after deleting "one". Repeating