Excerpts from Ernie Rael's message of Thu Sep 05 19:30:37 +0200 2013: > If I saw things correctly, select is run under a timer. Even if (I didn't check) the timer would not fire because no gtk event loop will be run as long as vim is executing python code ?
What is happening exactly? While VimL is running vim calls a "run gui event loop" occasionally, to found out that ctrl-c was pressed (otherwise you cannot abort viml). Why does this fail for python? You cannot tell pyton "let me run my event loop occasinally to find out whether ctrl-c was pressed", because you cannot patch the python interpreter implementetation. For this reason I think we need two threads: one for the event loop, one running python. the PyError function I talked about is thread safe (I looked it up) If we get started with this all, we can try to fix other issues as well. This will need da lot of: - work, dedication - support from the community (testing) - documenting the new ctrl-c behaviour If somebody knowing vim better than I do could comment on the "needs thread" thing - eg deny or acknowledege, then I'd know not doing the wrong thing. Marc Weber -- -- 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.
