We ignore (and should ignore) sigPIPE, because these errors are already caught because writes to a closed file handle throw exceptions. Moreover, if stderr is closed that leads to a sigPIPE, and we can't write to stderr anyways.
David On 8/11/08, Simon Michael <[EMAIL PROTECTED]> wrote: > I would like this functionality, to make darcs feel more responsive. I > don't understand the patch completely. It would be good to know why it > used to return () for PIPE. > > I tested the patch as follows: darcs get http://darcs.net and hit ctrl-c > one or more times near the beginning. You'll see there's a brief period > where it responds to ctrl-c's by printing the "in a sensitive operation" > warning, but it does not stop unless you press ctrl-c again after it has > left the sensitive section. > > After applying the patch and rebuilding, I saw.. the same thing ? > > _______________________________________________ > darcs-users mailing list > [email protected] > http://lists.osuosl.org/mailman/listinfo/darcs-users > _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
