#: 14249 S12/OS9/68000 (OSK)
    09-Feb-92  21:42:11
Sb: #14223-#Select
Fm: Bob van der Poel 76510,2203
To: Kevin Darling 76703,4227 (X)

Yeah, I forgot all about the lockout problem. Haven't tried it with a
non-interactive window. And if you switch windows to hit enter so that the
block goes away, well it defeats the purpose of the command .

Does the same thing happen when you do "(winsel;myprog)>>/w"? Since a shell
is being forked to handle the stuff in the line, I guess things are blocked
here too? It would be nice to have an elegant way to handle this. Hmmm, what
about having a prog. open a path to /w, select the new window and then start a 
shell there with "myprog" as a parm? Might be a lot of shells being forked, but
it should work. I just have to write a "open new window, select it and run a
program in it" program. Opps, not that simple. I'd have to close stdin, etc.
first so that the new program can use it's own paths.

Hmmm, and then there is still the problem of returning to the original
screen--esp. if the paths have been closed. Oh, guess they could be duped to
higher numbers... will give this some thought, play and let you know.

There is 1 Reply.