Bram Moolenaar wrote: > Skywind wrote: > > > Bram Moolenaar wrote： > > > > This will not break the plugins, and will make ch_read better. > > > > It could be used in a timer for congestion control manually. > > > > > > That changes what you get back, that is a bit strange. > > > How about adding a function that returns whether there is something to > > > read? Could call it ch_canread(). > > > > > > > I think "ch_canread()" is a nice design ! > > Please try out patch 8.0.0103, it should no longer get stuck. >
After trying 8.0.0103 several times on windows/mac/debian(via ssh), I believe stuck issue is fixed. however, cpu usage is still high with this test (exceeds 92%), and I can feel the lag between a keystroke and screen update, especially through a ssh terminal. At first I suppose my network bandwidth is fully filled with UI/quickfix update messages. After removing the ":cbottom" lines, I find vim is still very busy (cpu usage exceeds 90%) even if UI is not updated in the job callback. -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
