On Tue, May 01, 2001 at 12:15:05AM -0400, Charles S. Wilson wrote:
>Christopher Faylor wrote:
>> WHAT ^C issue? What are we talking about?????
>>
>> The only issue I'm aware of is being unable to stop a cygwin process if
>> all of its standard input/output has been redirected. That was fixed
>> a couple of days ago but it was hardly a new problem.
>
>That's the most recent appearance. Perhaps I'm misremembering, but I
>had thought there were several "signal-handling" things that have
>cropped up since January. CTRL-Z not suspending windows apps, CTRL-C
>not able to interrupt a process (regardless of whether its I/O was
>redirected), ...
CTRL-Z was an issue. CTRL-Z is a very special animal as far as signals
go.
CTRL-C was not an issue, AFAIK.
Regardless, the simple fix that was proposed a few days ago only solves
one specific problem. The problem that was fixed has been in cygwin
for quite a while.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
