Mercurial > vim
comparison runtime/doc/message.txt @ 18343:375a7ecdb351
Update runtime files.
Commit: https://github.com/vim/vim/commit/2e693a88b24dc6b12883fad78ff2cb9cd4469c98
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Oct 16 22:35:02 2019 +0200
Update runtime files.
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Wed, 16 Oct 2019 22:45:04 +0200 |
| parents | cc953757ed2a |
| children | 11394af51615 |
comparison
equal
deleted
inserted
replaced
| 18342:fedab77fee7b | 18343:375a7ecdb351 |
|---|---|
| 478 out-of-memory situation. First make sure that any changes are saved. Then | 478 out-of-memory situation. First make sure that any changes are saved. Then |
| 479 try to solve the memory shortage. To stay on the safe side, exit Vim and | 479 try to solve the memory shortage. To stay on the safe side, exit Vim and |
| 480 start again. | 480 start again. |
| 481 | 481 |
| 482 If this happens while Vim is still initializing, editing files is very | 482 If this happens while Vim is still initializing, editing files is very |
| 483 unlikely to work, therefore Vim will exit with value 123. | 483 unlikely to work, therefore Vim will exit with value 123. |
| 484 | 484 |
| 485 Buffers are only partly kept in memory, thus editing a very large file is | 485 Buffers are only partly kept in memory, thus editing a very large file is |
| 486 unlikely to cause an out-of-memory situation. Undo information is completely | 486 unlikely to cause an out-of-memory situation. Undo information is completely |
| 487 in memory, you can reduce that with these options: | 487 in memory, you can reduce that with these options: |
| 488 - 'undolevels' Set to a low value, or to -1 to disable undo completely. This | 488 - 'undolevels' Set to a low value, or to -1 to disable undo completely. This |