On Wednesday, January 15, 2014 4:44:34 AM UTC-6, Ashley Hewson wrote: > Thiago, > > I would love this to work and I thank you for your effort, but I'm quite > doubtful that vgetc can be safely run in a background thread. It simply does > too much work. Just to pick one example, it appears to be responsible for > blinking the GUI cursor while it's waiting, which will obviously conflict > with any screen updates the main thread is doing.
I thought the idea of this patch, was to allow background threads to send Vim a message, that says "when you get a chance, run function X". Then, at some later point in time, when Vim is not busy, it will run function X *IN THE MAIN THREAD*. Thus there should be no conflict between the deferred function and the main thread. Am I correct in this? If so, plugin authors must simply ensure that function X is threadsafe with the background functions in the same thread. This probably means making sure that the background thread is DONE with whatever data function X will access, until function X can run and is done with that data. -- -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
