This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: use of cut in guile-doc-snarf
- To: Michael Livshin <mlivshin at bigfoot dot com>
- Subject: Re: use of cut in guile-doc-snarf
- From: "Greg J. Badros" <gjb at cs dot washington dot edu>
- Date: 21 Jun 2000 07:32:59 -0700
- Cc: Brad Knotwell <knotwell at ix dot netcom dot com>, guile at sourceware dot cygnus dot com
- References: <200006201433.HAA23900@ix.ix.netcom.com> <s3bt0vwdzy.fsf@bigfoot.com>
Michael Livshin <mlivshin@bigfoot.com> writes:
> Brad Knotwell <knotwell@ix.netcom.com> writes:
>
> > Hello all--
> >
> > I was poking around at guile-doc-snarf and figured out why it takes such
> > a long time. In general, the following sed command takes an extremely
> > long time to complete:
> >
> > sed 's/^\(.\{128\}.\{128\}.\{128\}.\{128\}.\{128\}.\{128\}.\{128\}.\{128\}\).*/\1/g'
> >
> > As far as I can tell, the whole purpose of this command is to cut a line down
> > to 1024 characters in length. Is there any reason not to do something like
> > the following instead:
<snip>
The log message claims that the lines were intended to be trimmed to 512
characters:
revision 1.12
date: 2000/05/22 14:03:37; author: cmm; state: Exp; lines: +3 -1
* guile-doc-snarf.in: put the preprocessed file through sed to
trim all lines to 512 chars. I hope it doesn't break anybody's
shell. we'll see.
<snip>
Greg