Lines Matching refs:changes

22 u			Undo [count] changes.
31 CTRL-R			Redo [count] changes which were undone.
37 U			Undo all latest changes on one line, the line where
41 The last changes are remembered.  You can use the undo and redo commands above
43 changes again, getting back the text before the undo.
50 The "U" command will always mark the buffer as changed.  When "U" changes the
51 buffer back to how it was without changes, it is still considered changed.
52 Use "u" to undo changes until the buffer becomes unchanged.
59 In the Vim way, "uu" undoes two changes.  In the Vi-compatible way, "uu" does
83 One undo command normally undoes a typed command, no matter how many changes
84 that command makes.  This sequence of undo-able changes forms an undo block.
92 :undoj[oin]		Join further changes with the previous undo block.
94 			properly undoing changes.  Don't use this after undo
119 branch off.  This happens when you undo a few changes and then make a new
120 change.  The undone changes become a branch.  You can go to that branch with
126 :undol[ist]		List the leafs in the tree of changes.  Example:
127 			   number changes  when               saved ~
136 			The "changes" column is the number of changes to this
160 			When changes were made since the last write
186 Don't be surprised when moving through time shows multiple changes to take
357 The number of changes that are remembered is set with the 'undolevels' option.
374 When all changes have been undone, the buffer is not considered to be changed.
377 actually changes the buffer, compared to what was written, so the buffer is
381 Only changes completely within a fold will keep the fold as it was, because