Mercurial > vim

comparison runtime/doc/undo.txt @ 799:6beb2c667935

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
updated for version 7.0b
author vimboss
date Fri, 24 Mar 2006 22:21:52 +0000
parents 8c0b00d50acf
children 9f345c48220b
comparison
equal deleted inserted replaced
798:95dac6af3b3a 799:6beb2c667935
1 *undo.txt* For Vim version 7.0aa. Last change: 2006 Mar 21 1 *undo.txt* For Vim version 7.0b. Last change: 2006 Mar 24
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
111 Above we only discussed one line of undo/redo. But it is also possible to 111 Above we only discussed one line of undo/redo. But it is also possible to
112 branch off. This happens when you undo a few changes and then make a new 112 branch off. This happens when you undo a few changes and then make a new
113 change. The undone changes become a branch. You can go to that branch with 113 change. The undone changes become a branch. You can go to that branch with
114 the following commands. 114 the following commands.
115 115
116 What matters here is the order in which the changes are made. Undo and redo 116 This is explained in the user manual: |usr_32.txt|.
117 are not considered changes in this context. After each change you have a new
118 state of the text.
119 117
120 *:undol* *:undolist* 118 *:undol* *:undolist*
121 :undol[ist] List the leafs in the tree of changes. Example: 119 :undol[ist] List the leafs in the tree of changes. Example:
122 number changes time ~ 120 number changes time ~
123 4 10 10:34:11 121 4 10 10:34:11