© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
There's a lot of missing information in this report.
I don't know what "foo-program" is, nor what "nyxt" is so that's not really an example of SBCL behavior at any rate.
As to the problem statement: "It outputs to stderr and then ... remove" - is this to imply that "It outputs to stderr" with success, i.e. visibly? Then I'm not sure what the point is.
Or is it meant to suggest that some output was placed in *ERROR-OUTPUT* which was buffered prior to closing stderr?
The solution could be to call (FORCE-OUTPUT) if you're asking how to make missing output appear.
SBCL's *error-output* is line-buffered, the same as stdio's stderr.
(I'm assuming that "removed" means "closed" - "removed" is not a concept that pertains to a file descriptor, though it may pertain to an on-disk object)
If you're asking to have no condition be raised when a file descriptor is not writable, then I don't know why you would want that.