RENTSCH@USC-ECL@sri-unix (06/27/82)
Date: 15 Jun 1982 1714-PDT Several times we have observed terminals getting into funny states, sometimes during "write foo" sessions. The funny states are characterized by having many special character codes vacant (or set to NULL, I suppose), such as EOF, INTR, and suchlike. If the user is typing at the shell, and he realizes the problem, he can fix it, of course. But if he is in write, or some similar open-ended thing (yes is the canonical horrifying example) he is stuck. It's easy to kill the process and start things over again after fixing them up, but I would like to think there is a better solution. Has anybody else run into this before? Have you come up with a solution (or even a clear statement as to what the problem is or where it comes from?) Thanks, Tim Rentsch