[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue GC-MESSAGES (Version 2)
- To: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Subject: Issue GC-MESSAGES (Version 2)
- From: David A. Moon <Moon@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Fri, 30 Dec 88 19:26 EST
- Cc: CL-Cleanup@SAIL.Stanford.EDU
- In-reply-to: <881114101307.3.KMP@BOBOLINK.SCRC.Symbolics.COM>
I still think that focussing on GC messages is wrong, and instead there
should be a form that disables unsolicited typeout in general,
regardless of its source. Of course in some operating systems it might
be impossible to disable some forms of unsolicited typeout, and in other
operating systems unsolicited typeout might not exist (that is,
asynchronous messages might always come out in a separate window).
Thus this facility would just do the best effort appropriate for
the particular implementation.
I think there should be a stream argument, since there might be more
than one possible place for unsolicited typeout. In other words,
(WITHOUT-UNSOLICITED-OUTPUT (<stream>) <body>...) means that the output
send by <body> to <stream> should appear as a unit, without other
unsolicited output interspersed with it.
I don't think your :VERBOSE T option to encourage unsolicited typeout