On Aug 10, 9:31 am, ron <[email protected]> wrote: > On Aug 10, 4:34 pm, Ben Fritz <[email protected]> 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 really matters)? > > Running ReloadSession directly (or after sleep) in the main instance > doesn't work. > > The reason using the server call works (I think) is that it goes over > sockets, thereby passing the data off to the OS, so effectively > allowing vim to 'settle down' first.
Right, I was suggesting the following: call remote_send(v:servername, ":ReloadSession<cr>") instead of your: call remote_send(v:servername, ":sleep 100m|ReloadSession<cr>") By the way...clever workaround! I think what is happening is ReloadSession happens after Vim is done processing ALL the startup scripts and autocmd events, since it is a command coming from outside Vim. -- 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
