diff options
| author | Bram Moolenaar <Bram@vim.org> | 2010-05-24 11:59:29 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2010-05-24 11:59:29 +0200 |
| commit | 7db5fc838a7f701e495d41b0ff6a070591c84340 (patch) | |
| tree | ac8f061dafa07580e8b6cf3fedcd290a9f43d3ac /runtime/doc/undo.txt | |
| parent | 55debbe38429b81c0ce6e8400aef36812eb151d7 (diff) | |
| download | vim-git-7db5fc838a7f701e495d41b0ff6a070591c84340.tar.gz | |
Fix uninit memory read in undo code. Fix uint32_t in proto file.
A few minor changes.
Diffstat (limited to 'runtime/doc/undo.txt')
| -rw-r--r-- | runtime/doc/undo.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/runtime/doc/undo.txt b/runtime/doc/undo.txt index 05e5555b7..2c5568ea2 100644 --- a/runtime/doc/undo.txt +++ b/runtime/doc/undo.txt @@ -263,9 +263,10 @@ Reading an existing undo file may fail for several reasons: *E824* The version number of the undo file indicates that it's written by a newer version of Vim. You need that newer version to open it. Don't write the buffer if you want to keep the undo info in the file. -"Undo file contents changed" +"File contents changed, cannot use undo info" The file text differs from when the undo file was written. This means - the undo file cannot be used, it would corrupt the text. + 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* *E826* The undo file does not contain valid contents and cannot be used. *E827* The magic number at the end of the file was not found. This usually |