summaryrefslogtreecommitdiffstats
path: root/runtime/doc/undo.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2006-03-24 22:21:52 +0000
committerBram Moolenaar <Bram@vim.org>2006-03-24 22:21:52 +0000
commitc01140a1a069caf3ced83eac7d4866048c4b723e (patch)
tree0620c08894dcaf985d74e3cb76c682aecd7fb8ae /runtime/doc/undo.txt
parentdb552d60ec4613d5537d3ebdcc4130f1591c0589 (diff)
updated for version 7.0b
Diffstat (limited to 'runtime/doc/undo.txt')
-rw-r--r--runtime/doc/undo.txt6
1 files changed, 2 insertions, 4 deletions
diff --git a/runtime/doc/undo.txt b/runtime/doc/undo.txt
index 4ff7e20ce5..2a2d4783c8 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 21
+*undo.txt* For Vim version 7.0b. Last change: 2006 Mar 24
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -113,9 +113,7 @@ 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
-state of the text.
+This is explained in the user manual: |usr_32.txt|.
*:undol* *:undolist*
:undol[ist] List the leafs in the tree of changes. Example: