Re: Vim 7 performance notes

2007-02-10 Thread Bram Moolenaar
Alexei Alexandrov wrote: > Hi Bram Moolenaar, you wrote: > > > > > It sounds like keeping only 1024 bytes would already work for most > > situations. That would be an acceptable amount to keep allocated at > > all times. So why don't we use this as the initial size, and when it > > grows larg

Vim and OS versions

2007-02-10 Thread A.J.Mechelynck
Upgraded from novell-SUSE Linux 9.3 to openSUSE 10.2 My Vim compiled under 9.3 refuses to load: "perl.so not found". Recompiled (with make reconfig, same feature set). The new executable runs (with -ruby but I'll try to see about that). The display (with the same 'guifont') is *much* more good-loo

Re: Vim 7 performance notes

2007-02-10 Thread Alexei Alexandrov
Hi Bram Moolenaar, you wrote: > > It sounds like keeping only 1024 bytes would already work for most > situations. That would be an acceptable amount to keep allocated at > all times. So why don't we use this as the initial size, and when it > grows larger we free it when finished. The growth

Re: Vim 7 performance notes

2007-02-10 Thread Bram Moolenaar
Alexei Alexandrov wrote: > > This sounds like a bug in getc(). It should know that only one thread > > is reading the file and skip the locking. I don't think we should fix > > library bugs in Vim, unless it's crashing or another significant problem. > > > It can't be a bug. I might be missing

Re: Vim 7 performance notes

2007-02-10 Thread Alexei Alexandrov
Hi Bram Moolenaar, you wrote: >> It's Windows, but on Linux it should be similar. > > I would not assume it's similar until there is proof. > Of course. I'm going to investigate it there. > > This sounds like a bug in getc(). It should know that only one thread > is reading the file and skip