I just noticed that if I do a long recursive vimgrep, it filles the buffer list with hundreds of unloaded buffers for all the files that it looked at. Is there a way to manage this?
On 4/23/06, Eric Arnold <[EMAIL PROTECTED]> wrote: > I still can't find the dlls that work for perl or python. The Cygwin > perl 5.8 dll, cygperl5_88.dll, if renamed to perl588.dll causes gvim > to crash (big surprise..). > > I next tried Python, since I have both the Cygwin python, and the > Win32 download direct from the python site. Neither have a .ddl that > matches the gvim compile option, though the python version is correct. > > So, it becomes a general question. Where are the various .dll's for > Win32 Vim external interpreters? Heck, even Google returns nothing > for perl588.dll. :helpgrep \.dll doesn't talk about what/where they > are either. > > Maybe I'm missing some basic understanding of Vim's dynamic linking system? >
