🚀 go-pugleaf

In article <23314@watmath.waterloo.edu> grwalter@watmath.waterloo.edu (Fred Walter) writes:
>In article <171@hhb.UUCP> bvk@hhb.UUCP (Brett Kuehner) writes:
>>Is this when your zoo archive is in a directory with a lot of files in it? I
>>have a directory on my HD with about 50 files in it. If I do a
>>"zoo l foo.zoo", where foo.zoo is in that directory, zoo appears to thrash
>>on the drive a lot, possibly reading in the name of each file in the
>>HD directory (and very slowly). It will eventually list the archive, though.
>
>Yes this is what happens with me. I never before waited to see how long it
>would take for a listing to appear (1 MINUTE 26 SECONDS in a directory with
>93 files in it).

I've had it give me an error message something to the effect of "can't
find foo*.zoo", when I just asked for "foo".

If I type "zoo v foo" and I have foo.zoo and foobar.zoo in the
directory, it will list both, after much thrashing and seeking.  If I
ask for "foo.zoo", it still thrashes and seeks, but only lists
foo.zoo.

This is using zoo 2.0.  I much prefer zoo over arc, but this is my
biggest gripe.  I've had it spin for long minutes when trying to create
an archive in a very large directory.  (I switched to another cli and
added 100 buffers to dh0:, which helped.)


-- 
Eric Kennedy
ejkst@cisunx.UUCP