gVim 7 Win32 Maximize bug report

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

gVim 7 Win32 Maximize bug report

dotpanic-2
Hello,

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?

Thanks and best regards.
Mike Meirsman


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply | Threaded
Open this post in threaded view
|

Re: gVim 7 Win32 Maximize bug report

iler.ml
On 11/2/06, [hidden email]
<[hidden email]> wrote:

> Hello,
>
> 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

This problem was reported for Windows vim and fixed in the patch ~month ago.

But what is 7.0.262 ? Isn't ~ 158 the last patch number for vim7 ?

Yakov
Reply | Threaded
Open this post in threaded view
|

Re: gVim 7 Win32 Maximize bug report

dotpanic-2
Quoting Yakov Lerner <[hidden email]>:

>
> This problem was reported for Windows vim and fixed in the patch ~month ago.
>
> But what is 7.0.262 ? Isn't ~ 158 the last patch number for vim7 ?
>
> Yakov

I've just tested with the last version and it works quite well. Sorry  
to have bothered you with an already corrected bug.

Anyway, even with the latest release installed, the version displayed  
by windows is still 7.0.262.0.

Best regards,
Mike Meirsman

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Reply | Threaded
Open this post in threaded view
|

RE: gVim 7 Win32 Maximize bug report

Steve Hall-3
In reply to this post by dotpanic-2
From: dotpanic dotpanic homelinux.org, Thu, November 02, 2006 6:11 am

>
> 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?

I don't see it, but Vim has always had a weakness with long lines. For
me, the line takes more than 5 seconds to refresh on any movement, so
there is obviously some heavy duty processing going on somewhere.

Just curious, where does one download Vim 7.0.262 ? :)


--
Steve Hall  [ digitect dancingpaper com ]

Reply | Threaded
Open this post in threaded view
|

Re: gVim 7 Win32 Maximize bug report

iler.ml
On 11/2/06, Steve Hall <[hidden email]> wrote:

> From: dotpanic dotpanic homelinux.org, Thu, November 02, 2006 6:11 am
> >
> > 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?
>
> I don't see it, but Vim has always had a weakness with long lines. For
> me, the line takes more than 5 seconds to refresh on any movement, so
> there is obviously some heavy duty processing going on somewhere.
>
> Just curious, where does one download Vim 7.0.262 ? :)

Time machine ?

Yakov
Reply | Threaded
Open this post in threaded view
|

Re: gVim 7 Win32 Maximize bug report

Bill McCarthy
In reply to this post by dotpanic-2
On Thu 2-Nov-06 5:11am -0600, [hidden email] 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

Reply | Threaded
Open this post in threaded view
|

Re: gVim 7 Win32 Maximize bug report

A.J.Mechelynck
In reply to this post by dotpanic-2
[hidden email] wrote:

> Quoting Yakov Lerner <[hidden email]>:
>
>>
>> This problem was reported for Windows vim and fixed in the patch
>> ~month ago.
>>
>> But what is 7.0.262 ? Isn't ~ 158 the last patch number for vim7 ?
>>
>> Yakov
>
> I've just tested with the last version and it works quite well. Sorry to
> have bothered you with an already corrected bug.
>
> Anyway, even with the latest release installed, the version displayed by
> windows is still 7.0.262.0.
>
> Best regards,
> Mike Meirsman
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>

I don't know where that 4-part version number comes from. 262 can be
interpreted as 262d, 106h, 406o, ^F^A (the latter assumes one little-endian
word),... none of which rings any bells with me.

The "official" way to display the version number and patch level of any Vim
executable is (at the user's choice) any one of the following:

        vim --version |more
                Version number is displayed on the first line of output
                and "Included patches" (if any) on second line.
                Note: In Win32, "gvim --version" sends its output to a message
                popup, apparently after detaching Vim from the shell's stdout
                (if any) but without starting the GUI.

        launch [g]vim without any editfile. The splash screen comes up, unless
                the vimrc or some command-line switch sets the I flag in the
                'shortmess' option.
                Version and patchlevel are on the second non-blank line.

        :intro
                The splash screen comes up. Version & pl on 2nd nonblank line.

        :version
                The version listing comes up. Version on 1st line,
                included patches (if any) on 2nd.


Best regards,
Tony.
Reply | Threaded
Open this post in threaded view
|

Vim win32 version resource (was RE: gVim 7 Win32 Maximize bug report)

Vince Negri (ASL)
A.J.Mechelynck [mailto:[hidden email]] wrote:


> I don't know where that 4-part version number comes from. 262 can be
> interpreted as 262d, 106h, 406o, ^F^A (the latter assumes one little-endian
> word),... none of which rings any bells with me.

It comes from version.h:

#define VIM_VERSION_BUILD 262
#define VIM_VERSION_BUILD_BCD 0x106
#define VIM_VERSION_BUILD_STR "262"

Obviously we need a little script to keep this up to date...


Vince