From: Brian Mcbee (mcbeeb@atlantis.CS.ORST.EDU)
Date: 04/01/93


From: mcbeeb@atlantis.CS.ORST.EDU (Brian Mcbee)
Subject: Re: I maimed one VC.  What could have happened?
Date: 1 Apr 1993 22:19:51 GMT

In article <1993Mar31.145125.15186@wam.umd.edu> joel@wam.umd.edu (Joel M. Hoffman) writes:
>I don't know how this happened, but suddenly VC2 stopped working
>right. I think line 25 was screwing things up. For example, less
>wouldn't work, putting all the text on the last line of the screen.
>Thereafter, the screen wouldn't scroll until I typed ^L. I tried
>logging out and in again, but that didn't help. I verified that "stty
>-a" for that VC and another, working one, was the same. I verified
>that "set" likewise produced the same results. I tried echo ^V^O
>(under bash) and that didn't help. Rebooting helped a lot.

Hey! I've seen that one! Another one is: I usually run a 40 line console.
I can, however totally screw it up by loggin into a VAX and running EDT.
It changes that console to 25 lines, permanently as far as I can tell. I've
tried stty sane, setterm -reset, setterm -clear. The only way to fix, is
to reboot. I've looked at the termcap, and it *looks* right, but...
If anyone can come up with a solution, I'd sure have to reboot less often.