🚀 go-pugleaf

burhans@mizar.usc.edu (Mustang Sally) writes:

>Oops. Rereading the README file from cica.cica.indiana.edu I see
>that the date IS included with the INDEX file in the format
>YYMMDD. So I got the index and used the sort command to
>sort by that date. Works pretty good. Only problem is now I don't
>know what directory they are in. Well at least I learned something
>new.

Me too!  That was the only serious flaw to the ugly hack I posted to
get the recent file listings from the INDEX.  It would be nice to have
output similar to the "du" command with relative path info.

>warp12.zip	910430	Enterprise Spaceship (640x480x256)
>fish.zip	910430	640x480x16 Snapshot of Fish
>blank.zip	910430	1024x768x1 Black Bitmap (Why?!)
>disktool.zip	910429	Compliments FileManager (one click to move/delete/copy)
>winsaver.zip	910425	Restore Windows Session as You Left It
>rtf-desc.zip	910425	RichTextFormat Discussion
>cardfile.zip	910425	Discussion of Cardfile format

For instance, the first seven files came from three different
subdirectories.  I suppose it now appropriate to discuss the format of
the INDEX files.  I *could* add the subdirectory name on each line
since the individual INDEX files are created by hand anyway:

>fish.zip	910430	bmp	 640x480x16 Snapshot of Fish

However, since we've only got 79 columns, putting any more info onto
that line effectively reduces the space I have to put in a
description.   Especially if subdirectories become 2+ levels deep.
It's also redundant information when there's an individual index file
for each file are.  (Symbols or abbreviations for subdirectory names
may be too obscure.)

-- 

michael regoli
regoli@bronze.ucs.indiana.edu
regoli@iubacs.BITNET