Date: Tue, 10 May 2005 23:54:46 -0700
From: Mark Mitchell <mark@codesourcery.com>
CC: Eli Zaretskii <eliz@gnu.org>, bug-readline@gnu.org,
gdb-patches@sources.redhat.com
As Daniel says, the Ctrl-C issue is independent of this code, and, as
Chris says, it's perfectly possible to capture Ctrl-C under Windows; we
just don't want to do it here.
In the last sentence, what does ``here'' mean? Do you mean you don't
want to do it in Readline? If so, I think it's a mistake: the Unix
code of Readline clearly does manipulate signals, and I think a
Windows port should be as close to it as it can.