Re: size of gvim window on WIN32
- Dominic Evans wrote:
> You're lucky im a programmer and know what to do :)Thanks. Though apparently Bram was able to reproduce the error and fix
> Backtrace attached for the interested. It will be fixed by the 'if
> columns >' I mentioned earlier but I spose people may still want to
> know where the bug itself actually occurs.
it even before I saw your post below (I'm a little backward in ML
answering at the moment).
> On 30/09/05, A. J. Mechelynck <antoine.mechelynck@...> wrote:
>> Dominic Evans wrote:
>>> I'm afraid this doesn't work for me, the gui still seems to open at
>>> standard size.
>>> I also found a bug, its probably in vim6 as well but I was running
>>> vim7 alpha build. There doesn't seem to be any range checking done on
>>> the columns variable. So if it overflows it crashes vim.
>>> :set columns=999999999
>> Well, if it crashes gvim it's a bug. I suppose overflow checking (for
>> all numeric options) wouldn't be too hard a thing to do but I haven't
>> looked at the code. Could you produce a backtrace of the crash? Try
>> doing it with a debug build (i.e., gvimd.exe rather than gvim.exe) so
>> the backtrace will (hopefully) be easier to read for a human. If you can
>> reproduce the crash with a debug build, send your bug report (with the
>> backtrace) directly to Bram, I think he would be the man best able to
>> correct the problem.
>> In any case, 99999, or even 9999 or 999, should be enough to ensure that
>> the full width (or height) is used. gvim does check the value given
>> against the size of the viewport, so you will never get more lines or
>> columns than your screen is capable of handling. In some borderline
>> cases you may get just one less than what the "Maximize" menu item would
>> give you, but the discrepancy doesn't bother me overmuch.
>> Best regards,