Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!fmr
From: fmr@mcvax.cwi.nl (Frank Rahmani)
Newsgroups: comp.text
Subject: Re: vgrind questions - (nf)
Message-ID: <1713@mcvax.cwi.nl>
Date: Mon, 20-Apr-87 09:14:08 EST
Article-I.D.: mcvax.1713
Posted: Mon Apr 20 09:14:08 1987
Date-Received: Tue, 21-Apr-87 02:34:35 EST
References: <51000001@pbinfo.UUCP>
Organization: CWI, Amsterdam
Lines: 16
Summary: pagelength of vgrind output, different formatters

In article <51000001@pbinfo.UUCP>, michael@pbinfo.UUCP writes:
> 	- Is it possible to reduce the length of the text. Our
> 	`vgrind` writes very nice looking text, but too much to
> 	fit on one page. So some (1-3) lines are lost. How can I avoid this?
As the manpage clearly states (RTFM!!), lines beginning with '.' will
be passed unchanged to troff. So to get whatever pagelength you want
just prepend a line '.pl nu' to your input file, where n is the numerical
value and u de unit (cm|i|u) of your desired pagelength. Of course you
could also change the vgrind macro package.
> 
> 	- Did anybody convert `vgrind` to produce TeX output
> 	instead of troff output, i.e.: 
This means you need a new preprocessor for vgrind. Should be no problem if
you have sources. A much faster (and neater way) if you have Postscript
is using your PS laserprinter for the grinding. Just exchange troff for 
psroff in vgrind. You'll like the output!