James McCoy wrote:
> > It relaxes what the test is checking, I'm not sure that is needed. > > Did you check the example failures I mentioned in the commit? It's a > timing issue where many more iterations are able to happen between the > sub-vim being told what to do and the parent vim checking the result. I can understand that g:safe contains a higher count, that should be OK. g:again containing fewer "x", hmm, I suppose there is no guarantee we get four. Having "t" appear more than once should not happen, the timer is only triggered once. Perhaps the waiting time is too short? 50ms is just a guess. Only my system it already works with a 10ms wait. Let me make it 100ms to stay on the safe side. > > I'm wondering whether RunVimInTerminal() picks up the right Vim executable. > > The only vim executable in the chroot is the one created during the build. OK, that can't be the problem then. -- Laughing helps. It's like jogging on the inside. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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/202002231516.01NFGqnm012628%40masaka.moolenaar.net.
