".GIF" files

[Rex Fowler]

In article <659 at quad.sialis.com> dts at quad.sialis.com (David Sandberg) writes:
>In article <993 at gnosys.svle.ma.us> gst at gnosys.svle.ma.us (Gary S. Trujillo) writes:
>>I've never understood why some people insist on using cat(1) to get stuff
>>into the standard input of the lead program in a pipeline.  I claim that:
>>	cat a | b | c
>>is entirely equivalent in result to:
>>	b < a | c
>
>The latter may be functional equivalent, but it's not nearly as
>readable to my eyes.  The "path" by which the data "travels"
>starts in the middle of the command line, then jumps backwards to
>the start before leap-frogging forward to the end.  On the other
>hand, using cat(1) to feed the start of a pipeline gives you a
>nice "front-to-back" data path which is more readily apparent at
>the viewer's first glance.  (In my opinion, of course.)
>
>-- 
> \\         David Sandberg         \     ,=,       ,=,           \\
> //      dts at quad.sialis.com       /     | |uadric `=,ystems     //
> \\  uunet!umn-cs!sialis!quad!dts  \     `=\       `='           \\


If your into speed, use method 2.  If your into pretty, use method 1.
Method 1 creates an extra unnecessary process.  Of course, in the
case of viewing gif->pbm files, it's not very significant since the
conversions take so long anyway.

To save time viewing your GIF files, why not just keep them stored
as PBM files.  Then everytime you want to view one of them, its ready
to go..

% giftoppm filename.gif | ppmtopgm | pgmtopbm > filename.pbm
% pbmto3b1 filename.pbm
-- 
Rex Fowler <rmfowler%texrex at cirr.com>
UUCP:  egsner!texrex!rmfowler