You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Theoretically, there should be a way to poll vim and know when it's ready. Unfortunately, it's not as easy as it sounds.
Quoth dbarnett@:
I experimented with polling "--remote-expr 1" to see when vim is initialized, but that seems to not quite take care of it: tests still fail if we don't wait the full 0.5 seconds on startup. It looks like there's still a gap between when vim responds to "--remote-expr 1" and when it's actually "ready".
The text was updated successfully, but these errors were encountered:
My solution to this problem is to check vim --serverlist for the name of the server I'm currently spawning. Relevant code path is here -> here -> here.
I vaguely recall that I also started with a --remote-expr, and it worked, but I think I did it with a :write call, just to test it out, and I didn't want to leave it like that. I then moved on to the --serverlist method and didn't look back. Sending a --remote-expr 1 didn't even occur to me, that's pretty clever (even if it doesn't work :)).
So, I can't say for sure, but I guess your experiments are proof enough :).
Theoretically, there should be a way to poll vim and know when it's ready. Unfortunately, it's not as easy as it sounds.
Quoth dbarnett@:
The text was updated successfully, but these errors were encountered: