> > I'm not familiar with Vim's internals: please can you explain the > > different loops you're referring to here? > > Most callbacks are invoked from parse_queued_messages(). This is used > when waiting for a key and when sleeping. Only timer callbacks are > called elsewhere (and differently when using the GUI).
<snip> > > Per above, I'd be grateful if you could explain the significance of > > these different loops. > > It's hard to explain, and it differs per system and whether the GUI is > used. The general idea is "waiting for the user to type a character". > While doing that we trigger timers, read channels and process messages. Thanks. My understanding this fully is probably not significant to us reaching a solution here so if you'll excuse the odd silly question :) Did you see my suggestion about a bare-bones state() function? > Would a simple first cut of this be to expose the number of blocked > calls, e.g. ch_evalexpr and friends? We could then grow/add to this > function as we learn/experiment more? -- -- 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/CACoUkn51LDoEnessnDEaxpP7BeeVEdQVbq716tuM3z6V3AYsMw%40mail.gmail.com.
