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: guile at sourceware dot cygnus dot com
- Subject: Re: use of cut in guile-doc-snarf
- From: Robert Pluim <rpluim at nortelnetworks dot com>
- From: rpluim at bigfoot dot com
- Date: Wed, 21 Jun 2000 13:46:32 +0200 (CEST)
- References: <200006201433.HAA23900@ix.ix.netcom.com><s3bt0vwdzy.fsf@bigfoot.com>
- Reply-To: Robert Pluim <rpluim at nortelnetworks dot com>rpluim at bigfoot dot com
Michael Livshin writes:
> Brad Knotwell <knotwell@ix.netcom.com> writes:
> > 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:
> >
> > cut -c1-1023
>
> no reason, except the fact that I didn't know about this `cut' thing.
>
> duh!
>
> is the invocation you suggest above reasonably portable? (the whole
> `sed' exercise was done to circumvent the line length restriction in
> Solaris nawk, and now I just _expect_ such idiocies to lurk in every
> Unix tool I use).
While you're at it, you don't need to use 'cat ${temp} |' either. Both
"sed" and "cut" can take filename arguments. That would shave off
another few microseconds.
Robert
--
The above are my opinions,
and my opinions only.