turtle@sdsu.UUCP (Andrew Scherpbier) (02/02/89)
I have a 386 box running Xenix V 2.3.1. With this release there are a couple of programs which do things which I would like to do as well. The programs I am talking about are 'usemouse' and 'mscreen' Usemouse somehow inserts keystrokes between the keyboard and another program. This in itself would not be such an accomplishment since a simple filter could do that as well, but it seems completely transparent and it uses the /dev/ttyp* devices somehow. Mscreen also uses the /dev/ttyp* devices and it accomplishes the reverse of usemouse: it filters the output from a process and does special things when certain escape sequences come through. Here is the big question: How can I write a program to do this same sort of thing? -and- What are these /dev/ttyp* things anyway? Can anyone *Please* give me some clues on this? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~T~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "I sometimes get the feeling that | Andrew "Race Turtle" Scherpbier things cannot possibly get worse...| Computer Science Department and sure enough, they do." | San Diego State University --Don Perkins Jr. | ihnp4!jack!sdsu!turtle
jbayer@ispi.UUCP (Jonathan Bayer) (02/02/89)
In article <3458@sdsu.UUCP> turtle@sdsu.UUCP (Andrew Scherpbier) writes: > > I have a 386 box running Xenix V 2.3.1. With this release there are >a couple of programs which do things which I would like to do as well. >The programs I am talking about are 'usemouse' and 'mscreen' Usemouse >somehow inserts keystrokes between the keyboard and another program. >This in itself would not be such an accomplishment since a simple filter >could do that as well, but it seems completely transparent and it uses the ^^^^^^^^^^^^^^^^^^^^^^^^^^ Not quite. See below >/dev/ttyp* devices somehow. > Mscreen also uses the /dev/ttyp* devices and it accomplishes the reverse >of usemouse: it filters the output from a process and does special things >when certain escape sequences come through. > > Here is the big question: > > How can I write a program to do this same sort of thing? -and- What are >these /dev/ttyp* things anyway? > First, the usemouse is almost transparent. However, since it is sitting between the program and the tty the ioctl's get a little messed up. Specifically, I wanted to use uEmacs with a mouse. Unfortunately, when usemouse was running most of my function keys didn't work because the tty settings weren't being passed through. Second, the /dev/ttyp* are pseudo ttys. This means that you can use them as virtual terminals which programs can talk to. Finally, you will need the 2.3 developement system to be able to access the mouse devices. :-( Mscreen lets you get multiscreens on serial terminals, similar to the console. It works best on terminals that have several pages of memory. JB -- Jonathan Bayer Beware: The light at the end of the Intelligent Software Products, Inc. tunnel may be an oncoming dragon 19 Virginia Ave. ...uunet!ispi!jbayer Rockville Centre, NY 11570 (516) 766-2867 jbayer@ispi