Richard Stallman wrote:
The problem on w32 is that w32 sends a message to the process when delete-process is used. W32 then expects the process to answer to some w32 message (can't remember which one right now). Cygwin does not answer to this message. Then w32 shows a dialog box and asks the user what to do.>> Thanks. I did not notice and now I know why. When using Cygwin for >> the inferior process trying to use kill-find just hangs Emacs. So >> there is a bug here. >> >> kill-find now uses `delete-process'. Using `interrupt-process' or >> kill-process' works instead. Is there any reason not to use them? Or >> at least try them first?If delete-process does not work on Cygwin, that is a bug. Instead of proposing workarounds to avoid calling it, how about debugging it and fixing it?
IMO this is a bit inconvenient, but it could perhaps still be the best. But it works quite nicely AFICT with sending signals to Cygwin instead using interrupt-process or kill-process. So why not try these first and then shoot with delete-process if they do not work within a couple of seconds?
_______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
