On 2021-07-19, Bram Moolenaar wrote: > A simple way would be to not invoke the program directly from VimEnter, > but using a timer to run it a tiny bit later. > > Hmm, perhaps we could have an autocommand event that is triggered when > the codes that are expected have been received. Problem is though that > some requests may be unanswered, and then it would never trigger.
You could use a timeout to fix that. A few seconds should be sufficient. If a user's terminal never responds and the user gets tired of waiting that long, then they don't need the autocommand anyway. The timeout should be settable, and there should be a way to determine whether the autocommand was triggered by the terminal responses or by the timer expiring. Some v: variable, perhaps. Maybe just check for the presence of all the expected responses. Regards, Gary -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/20210719162057.GB14705%40phoenix.
