Stan in a couple posts on this one: > > I think Stan suggested a "release my terminal so that it can > > be opened by another process" command or function. > > Yes. > > Other techniques may work for selected people in selected > cases, but this provides a method that works for everyone. > I'd propose that the command be abortable via <break>. > I.e., if you "release your terminal", you remain logged on, > but no longer interacting with the CI. A "break" would > terminate the release and resume normal CI interaction. > Sort of a "PAUSE forever; RELEASE" functionality. I propose that Stan's above should be what the enhancement specifically asks for: This would be the ideal debugging set- up (at least for what I do). > > :RUN PROGNAME > FILENAME > > > > With the limited number of items on the ballot, and an > > easy workaround for this problem, I suggest that it be > > dropped from the list. > I don't. > > It's not a 100% solution ... > > Software that checks the terminal type won't work correctly. > Single character I/O may not work correctly. > Control-Y may not work correctly. ...etc. I also respectfully disagree with dropping this one: Besides Stan's above reasons, running the output to a file precludes realistic INTERACTIVE testing with VPLUS forms. We've had some pretty weird overlay problems & etc. in the past; I wouldn't want to lose full interactive testing capability.... Ken Sletten