Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!psuvax1!psuvm!cunyvm!ndsuvm1.bitnet!ud182050 From: UD182050@NDSUVM1.BITNET (Mike Aos) Newsgroups: comp.sys.apple2 Subject: Re: ProTERM Message-ID: <4210UD182050@NDSUVM1> Date: 1 Jul 90 09:03:43 GMT References: <469@beguine.UUCP> Organization: North Dakota Higher Education Computer Network, Fargo, ND Lines: 27 DISCLAIMER: Author bears full responsibility for contents of this article. In article <469@beguine.UUCP>, Greg.Bear@samba.acs.unc.edu (BBS Account) says: > >Does anyone know if the new ProTERM (v2.2) has corrected the problem of >newline mode in vt100 emulation and generating a new line when a character >appears in the 80th column? For the first, specifically the 20h and >20l vt100 commands need to be functional. Right now it just recognizes >the codes, but does not change anything. On the 80th column wrap, according >to other vt-100 terminals, when a letter appears in the 80th column, the >cursor will not move until the next character is sent. V2.1 generates a new >line, which messes up my usage of vi and reading messages/.sigs that use the >80th column. > > Greg.Bear@samba.acs.unc.edu I don't know if it fixes that problem specifically, but on BBS's that use ANSI, I can set it to VT100, and get by. It used to hand in some sections, and keep printing the same line on top of itself, but ProTerm v2.2 fixes that. It's a joy to work with (older versions of ProTerm always seems to die on occasion for me.) Mike ------- Mike UD182050@NDSUVM1 (.Bitnet?) UD182050@VM1.NoDak.Edu I got LOTSA opinions. You want one? You can have it!