[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: STANDARD-INPUT-INITIAL-BINDING (version 4)
- To: pierson@multimax.arpa
- Subject: Issue: STANDARD-INPUT-INITIAL-BINDING (version 4)
- From: Jim McDonald <edsel!jlm@labrea.stanford.edu>
- Date: Thu, 26 May 88 16:10:07 PDT
- Cc: cl-cleanup@sail.stanford.edu
- In-reply-to: Dan L. Pierson's message of Thu, 26 May 88 11:55:11 EDT <8805261555.AA18524@mist.UUCP>
> Moon says that *TERMINAL-IO* (and, by extension, *QUERY-IO*, and
> *DEBUG-IO*) should fail to work in a non-interactive environment where
> nothing like a terminal exists.
That seems like a needless restriction that could be rather painful
in particular instances.
What if I'm running a test suite that is trying to verify the
behavior of the debugger?
What if I want to redirect *termainal-io* through files to evade
limitations imposed by a given environment? (E.g., simulating TENEX
detach/attach in Unix, or running on a box with NFS but no terminal.)
What if I have a complex applications that started life being highly
interactive via *query-io*, and now has stabilized to the point where
people want to invoke it via canned scripts?
I'm having trouble imagining a situation where I would want
*terminal-io* to fail simply because Lisp was guessing that the
environment wasn't interactive.
jlm