On 2013-12-03 12:27, Nate Soares wrote:
> ./configure --with-features=tiny --enable-pythoninterp is
> sufficient to get a tiny vim configured with +eval, though this
> does indeed fail to compile. That said, I'm not confident that
> there is *no possible* compiling configuration in which vim is in
> "tiny" mode and eval is on.
While hackish, it depends on the particular source I'm looking at,
according to feature.h:
#ifdef FEAT_SMALL
# define FEAT_CMDHIST
#endif
/*
* Message history is fixed at 200 message, 20 for the tiny version.
*/
#ifdef FEAT_SMALL
# define MAX_MSG_HIST_LEN 200
#else
# define MAX_MSG_HIST_LEN 20
#endif
So the MAX_MSG_HIST_LEN is set based on whether FEAT_SMALL has been
defined. Coincidentally, if FEAT_SMALL is set, then FEAT_CMDHIST is
also defined, and if you look in eval.c, you'll see that you can test
for has('cmdline_hist') which is also only defined if FEAT_SMALL is
set. Thus
:echo has('cmdline_hist')?200:20
should be a reliable indicator of message-history size.
-tim
--
--
You received this message from the "vim_use" 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_use" 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/groups/opt_out.
