On Aug 10, 9:31 am, ron r...@ronware.org wrote:
On Aug 10, 4:34 pm, Ben Fritz fritzophre...@gmail.com wrote:
Vim is not multi-threaded, I doubt things are actually running during
the sleep. Or maybe you just need time for non-Vim stuff initiated by
Vim to finish? What happens if you
On Tuesday 10 August 2010 05:12:35 Tony Mechelynck wrote:
Well, 'lines', 'columns', 'guifont', 'guioptions', 'guicursor' can be
set, and the :winpos command issued, before the GUI is started, e.g. in
your vimrc (just remember to check :if has('gui_running') since they can
sometimes give
On Aug 10, 4:34 pm, Ben Fritz fritzophre...@gmail.com wrote:
Vim is not multi-threaded, I doubt things are actually running during
the sleep. Or maybe you just need time for non-Vim stuff initiated by
Vim to finish? What happens if you don't call sleep but just
ReloadSession (not that 100ms
On 07/08/10 19:24, ron wrote:
On Aug 6, 6:46 pm, Ben Fritzfritzophre...@gmail.com wrote:
I would certainly not consider the GUI sucessfully started until it
has been drawn at least once.
I am sure there is a way to suppress all the drawing until after
everything has 'settled'; VIM only
On Aug 6, 6:46 pm, Ben Fritz fritzophre...@gmail.com wrote:
I would certainly not consider the GUI sucessfully started until it
has been drawn at least once.
I am sure there is a way to suppress all the drawing until after
everything has 'settled'; VIM only knows if the GUI was started
On Aug 6, 9:46 am, ron r...@ronware.org wrote:
The GTK version shows the window being positioned and sized, etc,
*before* the GUIEnter event happens. This is distracting, as
sessions etc can resize the window, color schemes can be set, and so
on. The bouncing around of the window looks
