Mercurial > vim

comparison runtime/doc/undo.txt @ 15512:f0f06837a699

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update runtime files. commit https://github.com/vim/vim/commit/d09091d4955c5f41de69928f2db85611ed54ed23 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Jan 17 16:07:22 2019 +0100 Update runtime files.
author Bram Moolenaar <Bram@vim.org>
date Thu, 17 Jan 2019 16:15:08 +0100
parents 5c5908e81e93
children 0e473e9e70c2
comparison
equal deleted inserted replaced
15511:f41122780189 15512:f0f06837a699
1 *undo.txt* For Vim version 8.1. Last change: 2014 May 24 1 *undo.txt* For Vim version 8.1. Last change: 2019 Jan 04
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
256 Undo files are normally saved in the same directory as the file. This can be 256 Undo files are normally saved in the same directory as the file. This can be
257 changed with the 'undodir' option. 257 changed with the 'undodir' option.
258 258
259 When the file is encrypted, the text in the undo file is also crypted. The 259 When the file is encrypted, the text in the undo file is also crypted. The
260 same key and method is used. |encryption| 260 same key and method is used. |encryption|
261
262 Note that text properties are not stored in the undo file. You can restore
263 text properties so long as a buffer is loaded, but you cannot restore them
264 from an undo file. Rationale: It would require the associated text property
265 types to be defined in exactly the same was as before, which cannot be
266 guaranteed.
261 267
262 You can also save and restore undo histories by using ":wundo" and ":rundo" 268 You can also save and restore undo histories by using ":wundo" and ":rundo"
263 respectively: 269 respectively:
264 *:wundo* *:rundo* 270 *:wundo* *:rundo*
265 :wundo[!] {file} 271 :wundo[!] {file}