Pontus Leitzler wrote:
> I wrote the previous post yesterday but since it was my first it had
> to be moderated before showing up.
>
> Since then I did some more investigation and it turns out that the channel is
> indeed read in channel_read(...), but then the blocking select() prevents the
> incoming message to be processed.
> As soon as the blocking select returns (when I press a key),
> channel_parse_messages(...) is called and parses the buffer read before the
> select()-call.
>
> I expect that select() should be called with 0 timeout as long as the channel
> buffers haven't been processed entirely, is that a correct assumption? Should
> I write an issue in the github tracker?
So messages are ready to process, but Vim instead blocks on getting more
input? Can you find out where RealWaitForChar() is called from?
In inchar_loop() it should call parse_queued_messages() before blocking,
and if more input is needed set the wait time to 10.
--
hundred-and-one symptoms of being an internet addict:
260. Co-workers have to E-mail you about the fire alarm to get
you out of the building.
/// 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/201906240308.x5O384AU011577%40masaka.moolenaar.net.
For more options, visit https://groups.google.com/d/optout.
