#RUN LocksCLI
04-Jul-88 16:45:27
Sb: #133201-#RUN LocksCLI
Fm: Doug Winger 71001,1335
To: Christopher Tolmie 73657,3335
This message turned up in search, but its forum couldn’t be identified from the original transcript, so it may not be linked into its thread.
Chris,
Certain things grab the spawning CLI for use as Stderr, with some using it
for stdout and stdin as well. As long as they're still running they hold on
to the window. The well-behaved ones detach or open their own windows. Some
will allow themselves to be 'killed' (Snipit being a nice example) so you can
close the window. It's a case of operator beware, or choosing what you intend
to RUN carefully. Sometimes, a redirection to NIL: will help. e.g. RUN >NIL:
thingie >NIL: but not always.
The safest method is never to close the CLI when you've RUN something from it
unless you're sure that it hasn't grabbed the window. A quick check of each
thing will allow you to be sure of how it will behave.