Date: Wed, 4 Oct 2000 08:32:38 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: Doc for __dosexec_find_on_path()
In-Reply-To: <39DA5498.7648334C@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1001004083210.21716E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 3 Oct 2000, Richard Dawe wrote:

> > There's no automatic line breaks inside @example.  So breaking long
> > lines by hand is a Good Thing.
> 
> I've written a Perl script to detect when @example/@end example and
> @smallexample/@end smallexample sections exceed their respective maximum
> line lengths (72 and 74 from a previous mail of yours). The script is
> attached.

Thanks.

DJ, should we add this to djlsrNNN.zip?  Or at least introduce it into
CVS, along with the other scripts used when making the distro?

> I didn't change @example -> @smallexample, but I did fix the overly long
> lines. A large (~55K) diff is attached.

Thanks again.

> > Alternatively, we could change mkdoc.cc to do that automatically for us;
> > but I'm not sure how ugly will the automatic line breaks look.
> 
> I don't think that would be a very pretty option. My script is quick to
> run, so we can check frequently/before release if anything is broken.

I'm worried that any operation prior to release that must be done
manually, might be forgotten.  It happened to me before; it can happen
again to others as well.