mike@isi.UUCP (Mike Maloney) (04/22/89)
Hey SCO, is the initscr() function in curses (termcap version) setting the terminal input mode to RAW through stderr?? I am using curses to write to devices other than 'stdout'. I do this by opening the other device and then dup2'ing stdout and stdin to its file descriptor before calling initscr(). I start the task in the background so that the original terminal is freed for other stuff. I want to leave stderr pointing to the original terminal for various error messages. It worked great in the 2.2.2 development system of Xenix 386, but now after I start the program, the original terminal is left in RAW mode, requiring me to 'stty sane^J' -- somewhat of an annoyance. (The other solution is to call crmode(), echo(), and nl(), after initscr().) When I redirect stderr to an unused multi-screen on the command line thusly: $ testprog 2>>/dev/tty09 & the problem doesn't occur, leading me to believe that initscr() is using stderr. What gives (and why)? -- -------- Mike Maloney Integral Systems, Inc (301) 731-4233