Lennart Borgman <[EMAIL PROTECTED]> writes: > Richard Stallman wrote: >> >> 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? >> >> > 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.
AFAICS, delete-process invokes kill-process to kill the process; the rest of delete-process is just book-keeping. IIUC you say kill-process works (or is it only interrupt_process which works?) instead of delete-process ? But kill-process on cygwin should just invoke "cygwin kernel's kill" so why does the cygwin code use the w32 message interface? -- or am I missing something. > > 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? AFAICS, delete-process calls kill-process, so it looks like a loop in some of the book-keeping in delete-process ... can you find that loop? IOW, what is emacs doing when it "hangs" ? -- Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
