diff options
Diffstat (limited to 'runtime/doc/undo.txt')
| -rw-r--r-- | runtime/doc/undo.txt | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/runtime/doc/undo.txt b/runtime/doc/undo.txt index 46469b3533..fba981d4a3 100644 --- a/runtime/doc/undo.txt +++ b/runtime/doc/undo.txt @@ -256,9 +256,6 @@ message about that when opening a file. Undo files are normally saved in the same directory as the file. This can be changed with the 'undodir' option. -When the file is encrypted, the text in the undo file is also crypted. The -same key and method is used. |encryption| - You can also save and restore undo histories by using ":wundo" and ":rundo" respectively: *:wundo* *:rundo* @@ -321,13 +318,6 @@ Reading an existing undo file may fail for several reasons: the undo file cannot be used, it would corrupt the text. This also happens when 'encoding' differs from when the undo file was written. *E825* The undo file does not contain valid contents and cannot be used. -*E826* The undo file is encrypted but decryption failed. -*E827* The undo file is encrypted but this version of Vim does not support - encryption. Open the file with another Vim. -*E832* The undo file is encrypted but 'key' is not set, the text file is not - encrypted. This would happen if the text file was written by Vim - encrypted at first, and later overwritten by not encrypted text. - You probably want to delete this undo file. "Not reading undo file, owner differs" The undo file is owned by someone else than the owner of the text file. For safety the undo file is not used. |