Richard Giraud <[EMAIL PROTECTED]> added the comment: Given how easy it is to increase the limit, I'm guessing that the limit is a way of detecting and stopping runaway processes. If this is the case, then I don't consider this a bug; OS X is doing what it should and darcs is doing what it should.
A reasonable soultion woud be: - The item captured in the FAQ. - The exception caught and a useful error message displayed (a suggestion to try changing the limit, a link to the FAQ, etc.). I've updated the FAQ to include information about the issue and how to change the limit. __________________________________ Darcs bug tracker <[EMAIL PROTECTED]> <http://bugs.darcs.net/issue560> __________________________________ _______________________________________________ Cvs-ghc mailing list Cvs-ghc@haskell.org http://www.haskell.org/mailman/listinfo/cvs-ghc
