> Are you sure about that? No. If you use --nofork and if you press ctrl-c in the terminal you might be lucky.
However this is not enough because - people start vim from menu - people might not use --nofork Current implementation does not interrupt anything using but VimL even using --nofork (tested pyton and ruby) > Have you tried enabling SIGINT in gui mode? There is a problem: Its hard to know the pid unless you take notes upfront. Maybe you can send such a signal, but users are used to pressing "ctrl-c" in whatever window is active? > Though conceptually simple (?), things are spread out and there are > certainly other things to look out for. I don't have any feel for how > much work such a change would be. A lot, but having nice async support is something we should strive for :( I cannot afford hacking on Vim for days at the moment. So this has to wait in any case unless somebody is willing to fund such work. I'd also like to see at least 5 people wanting this to be fixed. We're two now. 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.
