Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!library.ucla.edu!europa.eng.gtefsd.com!uunet!psinntp!newstand.syr.edu!mothra.syr.edu!dhhoveme From: dhhoveme@mothra.syr.edu (David H. Hovemeyer) Subject: Re: Vt52 problem with vi on NetBSD 0.9 Message-ID: <1993Sep25.164758.6457@newstand.syr.edu> Organization: Syracuse University, Syracuse, NY References: <1993Sep22.003221.23217@jupiter.sun.csd.unb.ca> <1993Sep22.095753.881@cc.usu.edu> Date: Sat, 25 Sep 93 16:47:57 EDT Lines: 29 In article <1993Sep22.095753.881@cc.usu.edu> ivie@cc.usu.edu writes: >In article <1993Sep22.003221.23217@jupiter.sun.csd.unb.ca>, douc@jupiter.sun.csd.unb.ca (D. Doucet) writes: >> 0.8 >> had no trouble talking to my vt52 terminal through com0. 0.9 >> however, has problems when I try to run programs like vi or more >> that use escape characters and what not. After these commands, I >> get a bunch of reverse, block unprintables and so on. > >That's odd. My VT52s are incapable of doing stuff like reverse video. Maybe >I misunderstood what you said... > >You might look in some news archives. There was some discussion a while ago >(i think in the .bugs group) about vi and more doing strange things to >the terminal settings; changing from 8 bits & no parity to 7 bits & even >parity type of stuff. I had precisely the same experience with 0.8 vs 0.9 with my vt102. The problem is that getty is dropping parenb (i.e., not asserting parity control). My impression (from the discussion in .bugs) was that this was a fairly fundamental problem, requiring some kind of wizardry to fix. If you are curious, you can run stty on the console and see that parenb gets changed to -parenb when you run programs like vi and more. Dave -- dhhoveme@rodan.syr.edu