> I am on the fence on this one. > If Vim shells out to run something and that something is taking a _very_ long > time, your Vim is essentially hung. > This happens to me frequently. > At least with the Window there, I can close it, which returns an error to Vim > (via the system() call) and I get my Vim back. > Without that I have to terminate Vim, and that is a real pain. > > David -------------- So, how can you stop these __very__ long time tasks from non-windows platform, which won't pop up a cmd window ?
__very__ long time tasks are supposed to be launched via async jobs in the latest vim version. Could windows gvim stop the child processes by a Ctrl_C/Ctril_Break ? There is an internal win32 message loop at line 4159 of os_win32.c: https://github.com/vim/vim/blob/master/src/os_win32.c#L4159 which is used to update gui while waiting for child process finished. Can we add a Ctrl_C/Ctrl_Break detection there to allow user stop a long time running process ? (I haven't read the whole part of os_win32.c, just do some search and find this routine.) If the child processes of 'system()' could be stop by ctrl_break/ctrl_c, could we make `system()` act the same way to the other vim versions ? -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
