summaryrefslogtreecommitdiffstats
path: root/runtime/doc/message.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2010-07-26 22:21:27 +0200
committerBram Moolenaar <Bram@vim.org>2010-07-26 22:21:27 +0200
commit0ed0eea20689b3bdafe296f4e132679d3977b943 (patch)
tree98c323889cb76e5475f62983f79717c7b30adff8 /runtime/doc/message.txt
parentf82bac371703d25bf94d3a91bc68413d3f734be7 (diff)
Updated runtime files.
Diffstat (limited to 'runtime/doc/message.txt')
-rw-r--r--runtime/doc/message.txt13
1 files changed, 11 insertions, 2 deletions
diff --git a/runtime/doc/message.txt b/runtime/doc/message.txt
index c4ed18b0d3..d534cab45b 100644
--- a/runtime/doc/message.txt
+++ b/runtime/doc/message.txt
@@ -1,4 +1,4 @@
-*message.txt* For Vim version 7.3c. Last change: 2010 Jul 20
+*message.txt* For Vim version 7.3c. Last change: 2010 Jul 26
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -467,7 +467,16 @@ Oh, oh. You must have been doing something complicated, or some other program
is consuming your memory. Be careful! Vim is not completely prepared for an
out-of-memory situation. First make sure that any changes are saved. Then
try to solve the memory shortage. To stay on the safe side, exit Vim and
-start again. Also see |msdos-limitations|.
+start again.
+
+Buffers are only partly kept in memory, thus editing a very large file is
+unlikely to cause an out-of-memory situation. Undo information is completely
+in memory, you can reduce that with these options:
+- 'undolevels' Set to a low value, or to -1 to disable undo completely. This
+ helps for a change that affects all lines.
+- 'undoreload' Set to zero to disable.
+
+Also see |msdos-limitations|.
*E339* >
Pattern too long