On 16/12/2015 19:14, Christian Brabandt wrote:
[HAVE_AVAIL_MEM]
However, it does throw out the setting of maxmem/maxmemtot with it.
The setting of maxmem/maxmemtot should be under a separate control
IMHO.
Yes that I thought as well.
I remember when I debugged the blowfish corruption bug on Windows I
wondered why the maxmem/maxmemtot setting was so much lower than on
Linux. I wanted to suggest increasing that setting on Windows as well,
but forgot about it.
The simplest fix is to up the default values for maxmem and maxmemtot on
Win32 to match the values for unix:
diff --git a/src/os_win32.h b/src/os_win32.h
--- a/src/os_win32.h
+++ b/src/os_win32.h
@@ -123,11 +123,11 @@
#define TEMPNAMELEN _MAX_PATH /* length of temp file name path */
#ifndef DFLT_MAXMEM
-# define DFLT_MAXMEM (2*1024) /* use up to 2 Mbyte for a buffer */
+# define DFLT_MAXMEM (5*1024) /* use up to 5 Mbyte for a buffer */
#endif
#ifndef DFLT_MAXMEMTOT
-# define DFLT_MAXMEMTOT (5*1024) /* use up to 5 Mbyte for Vim */
+# define DFLT_MAXMEMTOT (10*1024) /* use up to 10 Mbyte for Vim */
#endif
/*
I had a look at resurrecting mch_avail_mem() and using the argument to
just do something for initialisation, but there isn't any consistently
reasonable value that can be returned as it depends what the machine is
doing at the moment you start VIM. Its most likely more effort than its
worth.
HTH - TTFN
Mike
--
Any discipline for a cat that does not involve petting that cat will
backfire.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
