Chris Marshall via RT wrote:
Tue Jul 13 12:59:28 2010: Request 59322 was acted upon.
Transaction: Ticket created by CHM
Queue: Win32-Console
Subject: SetConsoleCtrlHandler function not supported
Broken in: 0.09
Severity: Important
Owner: Nobody
Requestors: c...@cpan.or
Wed Jul 14 20:00:48 2010: Request 59322 was acted upon.
Transaction: Correspondence added by dbec...@roadrunner.com
Queue: Win32-Console
Subject: Re: [rt.cpan.org #59322] SetConsoleCtrlHandler function not
supported
Broken in: 0.09
Severity: Important
Owner: Nobody
Requ
Wed Jul 14 21:15:20 2010: Request 59322 was acted upon.
Transaction: Correspondence added by CHM
Queue: Win32-Console
Subject: SetConsoleCtrlHandler function not supported
Broken in: 0.09
Severity: Important
Owner: Nobody
Requestors: c...@cpan.org
Status: open
Tic
Wed Jul 14 21:23:06 2010: Request 59322 was acted upon.
Transaction: Correspondence added by CHM
Queue: Win32-Console
Subject: SetConsoleCtrlHandler function not supported
Broken in: 0.09
Severity: Important
Owner: Nobody
Requestors: c...@cpan.org
Status: open
Tic
Thu Jul 15 05:30:45 2010: Request 59322 was acted upon.
Transaction: Correspondence added by dbec...@roadrunner.com
Queue: Win32-Console
Subject: Re: [rt.cpan.org #59322] SetConsoleCtrlHandler function not
supported
Broken in: 0.09
Severity: Important
Owner: Nobody
Requ
Chris Marshall via RT wrote:
So the problem appears that the 1st Ctrl-C is caught
but something in the readline part prevents reloading
of the signal handler so an immediate Ctrl-C will
send another "SIGINT" which will not be caught and
then the console control handler will be called which
offer
Thu Jul 15 09:19:27 2010: Request 59322 was acted upon.
Transaction: Correspondence added by CHM
Queue: Win32-Console
Subject: SetConsoleCtrlHandler function not supported
Broken in: 0.09
Severity: Important
Owner: Nobody
Requestors: c...@cpan.org
Status: open
Tic
