Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.bugs.sys5
Subject: Re: bug in pg on System V
Keywords: pg autowrap no-newline
Message-ID: <10059@smoke.BRL.MIL>
Date: 17 Apr 89 06:45:56 GMT
References: <4935@ingr.com> <464@b11.INGR.COM> <10038@smoke.BRL.MIL> <1096@vsi.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 19

In article <1096@vsi.COM> friedl@vsi.COM (Stephen J. Friedl) writes:
>VT100 deferred autowrap waits until it receives the 81st character
>on a line before thinking about an autowrap.  If this character is
>printable, wrap occurs before it is printed, but if the character is
>a newline then it is only done once.

No, that's the intention, but the actual VT100 implementation has
numerous glitches in its 8085 microcode.  As I said, the exact
behavior is exceedingly baroque.

>the capname "xenl".

That's an abuse of that capability; it still doesn't handle all the
VT100 weirdness because the exact internal state of the VT100
microcode is not and cannot be simulated in such simple terms.
Perhaps later VT models such as the VT220 are not quite so badly
broken (in other words, don;t quite emulate a VT100); I don't know.

We go through this discussion every couple of years.