Re: making less faster on large amounts of stdin data

> > > John Summerfield wrote: > > > This is a silly, negative response. If the patch does what Wojtek says, > > the IMV it should be applied to the source. > > > A patch to speed up a strange use of a program is what > seams silly. less (and more) are interactive. why use > them in a non int

Re: making less faster on large amounts of stdin data

John Summerfield wrote: > This is a silly, negative response. If the patch does what Wojtek says, > the IMV it should be applied to the source. A patch to speed up a strange use of a program is what seams silly. less (and more) are interactive. why use them in a non interactive way? What's t

Re: making less faster on large amounts of stdin data

This is a silly, negative response. If the patch does what Wojtek says, the IMV it should be applied to the source. It has no significant impact on its size. I can't tell whether there's an adverse impact on small machines - if so, then it needs to caclulate a buffer size and use the and that

Re: making less faster on large amounts of stdin data

Wojtek Pilorz wrote: > > try the following (on a machine with 128M or more of RAM): > > time perl -e '$n=80; $o=0; > for ($i=1;$i<= $n; ++$i) { > $l=sprintf "%s line %8d, offset %10d\n", "="x16, $i, $o; > print $l; > $o