Re: gVim 7 Win32 Maximize bug report
- dotpanic@... wrote:
> Quoting Yakov Lerner <iler.ml@...>:I don't know where that 4-part version number comes from. 262 can be
>> 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 ?
> 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.
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
Version and patchlevel are on the second non-blank line.
The splash screen comes up. Version & pl on 2nd nonblank line.
The version listing comes up. Version on 1st line,
included patches (if any) on 2nd.
- A.J.Mechelynck [mailto:antoine.mechelynck@...] wrote:
> I don't know where that 4-part version number comes from. 262 can beIt comes from version.h:
> interpreted as 262d, 106h, 406o, ^F^A (the latter assumes one little-endian
> word),... none of which rings any bells with me.
#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...