Mercurial > vim

comparison runtime/doc/undo.txt @ 2251:646d34788036 vim73

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Fix a few compiler warnings. Fix crash with encrypted undo file.
author Bram Moolenaar <bram@vim.org>
date Sun, 06 Jun 2010 14:20:26 +0200
parents 6d3d35ff2c2b
children 941ff1cd317a
comparison
equal deleted inserted replaced
2250:1bac28a53fae 2251:646d34788036
283 "File contents changed, cannot use undo info" 283 "File contents changed, cannot use undo info"
284 The file text differs from when the undo file was written. This means 284 The file text differs from when the undo file was written. This means
285 the undo file cannot be used, it would corrupt the text. This also 285 the undo file cannot be used, it would corrupt the text. This also
286 happens when 'encoding' differs from when the undo file was written. 286 happens when 'encoding' differs from when the undo file was written.
287 *E825* The undo file does not contain valid contents and cannot be used. 287 *E825* The undo file does not contain valid contents and cannot be used.
288 *E826* The undo file is encrypted but decryption failed.
289 *E827* The undo file is encrypted but this version of Vim does not support
290 encryption. Open the file with another Vim.
291 *E832* The undo file is encrypted but 'key' is not set, the text file is not
292 encrypted. This would happen if the text file was written by Vim
293 encrypted at first, and later overwritten by not encrypted text.
294 You probably want to delete this undo file.
288 "Not reading undo file, owner differs" 295 "Not reading undo file, owner differs"
289 The undo file is owned by someone else than the owner of the text 296 The undo file is owned by someone else than the owner of the text
290 file. For safety the undo file is not used. 297 file. For safety the undo file is not used.
291 298
292 Writing an undo file may fail for these reasons: 299 Writing an undo file may fail for these reasons: