Comment #4 on issue 103 by [email protected]: Python thread are not running in background
http://code.google.com/p/vim/issues/detail?id=103
I also use Python2 for the test, but I use both pythoninterp=dynamic and python3interp=dynamic on amd64 and AFAIR non-dynamic python2-only builds on arm. Maybe this matters.
Why this is not an option? If caches that are talked about are per-process ones you can just move all libclang-related code to the separate process; you are not likely to have performance impact notable by user. And processes are forcefully terminatable, so “shutdown of vim takes several seconds” or “unable to quit vim when thread is running” issues should not appear.
-- 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
