[ingr.general] bug in pg on System V

nik@ingr.com (Nik Simpson) (04/12/89)

SVR3.1 version of pg behaves strangely when pressented with a file where the
lines are exactly 81 characters long including the \n.  If your terminal is
set to autowrap you will see this behaviour.  If the terminal is not set to
autowrap then pg clearly fails to generate newlines so the document does not
print sensibly.

	This behaviour was first observed on a Intergraph 3050 workstation
running CLIX 3.1 which is the Intergraph Licensed version of AT&T SVR3.1.
 |----------------------------------------------------------------------|
 |                                                                      |
 |       Disclaimer                                                     |
 |               The author denies any responsibility for               |
 |       anything you disagree with,  He was on holiday at              |
 |       the time.                                                      |
 |                                                                      |
 |----------------------------------------------------------------------|
 
		Nik Simpson
		Senior Systems Engineer
 		System Technology Marketing Group
		Intergraph UK Ltd.
 		ph +44-793-619999x333 (voice)
		ph +44-793-618508 (fax)
 		UUCP		: uunet!ingr!nik
 		From HSV	: ingr!nik (will be forwarded)
 		From Europe	: swndn!st_nik!nik
 		Internet	: nik@INGR.COM

guy@b11.INGR.COM (Guy Streeter) (04/12/89)

In article <4935@ingr.com> nik@ingr.com (Nik Simpson) writes:
>
>SVR3.1 version of pg behaves strangely when pressented with a file where the
>lines are exactly 81 characters long including the \n.  If your terminal is
>set to autowrap you will see this behaviour.  If the terminal is not set to
>autowrap then pg clearly fails to generate newlines so the document does not
>print sensibly.

There is nothing wrong with the way pg behaves (at least, not that I
can see).

pg uses the terminfo terminal information to determine how it should
act.  If your TERM environment variable is set to VT200, VT220, or
VT100 (among others), programs which use this information (pg, rn,
editors, etc.) will understand that your terminal has 'automatic
margins'.  Changing the terminal setup does not change terminfo's
understanding of your terminal capabilities.  If you want pg to know
that your terminal does not auto-wrap, you must set your TERM
environment variable to the name of a suitable terminfo definition.

The auto-wrap function of the DEC VTxxx-series does function in
exactly the way expected of the auto-margin capability of terminfo,
but that's another posting.

--
Guy "I am a VT220-nam32r" Streeter
ingr!b11!guy