Eli Zaretskii wrote:
Date: Sun, 07 Aug 2005 02:39:03 +0200
From: [EMAIL PROTECTED]
>>
I dunno if this is the case, IME if the parent has registered a
Ctrl-C handler it may need to set CREATE_DEFAULT_ERROR_MODE in
the "process creation flags" in the call to CreateProcess.
The Microsoft documentation seems to indicate this flag is not
relevant to Ctrl-C.
Yes, you'right. Controlling children appeared better with that flag, but
after more accurate testing I have to admit that it was wishful thinking.
I tested w98, nt4, and win2000 and found no way (except TerminateProcess)
to interrupt batch files running under command/cmd: GenerateConsoleCtrlEvent
reaches its currently active executable child which can catch it. But then
command/cmd carries on running the next batch line. (Perhaps, deleting the
batch file makes more sense here?)
_______________________________________________
Make-w32 mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/make-w32
