I have an occasional issue where my sessions do not restore the window
size correctly. This is in 7.3d, using GTK GUI (the issue may well
exist under Windows, but I haven't tried it there yet).
I have a rather complex sessions setup, but the point is that I save a
special value "WinColumns" (amon
This script replicates the problem, simply "gvim -u
test.vim" (assuming you call this 'test.vim')
set nocp
set viminfo=c,!,<1000,'1000
set
sessionoptions=globals,buffers,slash,localoptions,folds,tabpages,unix
fun TestLeave()
let g:WinCol=&columns
wv! test.viminfo
mks! t
Now confirmed that this does NOT happen on Windows, but does on GTK
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Ron Aaron wrote:
> I have an occasional issue where my sessions do not restore the window
> size correctly. This is in 7.3d, using GTK GUI (the issue may well
> exist under Windows, but I haven't tried it there yet).
>
> I have a rather complex sessions setup, but the point is that I save a
> s
On Aug 5, 10:56 pm, Bram Moolenaar wrote:
> GTK resizing is hacky. I could never figure out how to do it properly.
> I'm sure that when we try to fix this problem another one will pop up.
Arggh! Without really trying to understand the code, just by seeing
what happens using my test file, it se
On Thursday 05 August 2010 22:56:26 Bram Moolenaar wrote:
> GTK resizing is hacky. I could never figure out how to do it properly.
> I'm sure that when we try to fix this problem another one will pop up.
A simple addition of "gui_mch_update();" before doing the GUI_ENTER autocommand
seems to
Ron Aaron wrote:
> On Thursday 05 August 2010 22:56:26 Bram Moolenaar wrote:
>
> > GTK resizing is hacky. I could never figure out how to do it properly.
> > I'm sure that when we try to fix this problem another one will pop up.
>
> A simple addition of "gui_mch_update();" before doing the G
On Friday 06 August 2010 22:16:40 Bram Moolenaar wrote:
> Well, that's a low risc change, let me include that.
> I'm glad it was this simple.
As it turns out, it does not completely fix the problem (the 'test.vim' script
still occasionally fails), but it is much better than it was.
Not being fa
