On Thu 2-Nov-06 5:11am -0600, [EMAIL PROTECTED] wrote:
> I'm pretty new to this mailing list and I hope I'm posting at the
> right place. I just want to report a simple bug, easy to reproduce.
>
> I have only tested it on Windows.
>
> Open vim, write a single 10000 characters line (filled with blanks for
> example), and just maximize the window.
>
> On my PC, I get the following error:
>
> Vi Improved - A Text Editor has encountered a problem and needs to
> close. We are sorry blabla...
>
> The details are:
> AppName: gvim.exe AppVer: 7.0.262.0 ModName: gvim.exe
> ModVer: 7.0.262.0 Offset: 0012c053
>
> Is the problem reproducible on your configurations?
Running Gvim 7.0.158 on Win XP, I get no crash for 10,000+
character lines. I do get some unusual behavior. With
set fileformats=dos,unix,mac
I see a ^J as the first character of lines 2 through n+1
(for an n-line file) and my 'fileformat' is set to "mac."
[That would be expected behavior for reading a dos file as a
mac file, since the CR of dos's CR/LF would end the line and
LF (0x0A) would render as ^J.]
It rendered OK when I changes 'ffs' to "dos,unix" - IIRC,
Bram once mentioned that file format detection was a bit
weak on long lines.
BTW, I also see that Windows Explorer reports Gvim is at
version 7.0.262.0. Its copyright is for 1996-2005, its
trademark is Vim and the original file name is VIM.EXE?
--
Best regards,
Bill
