home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!jvnc.net!netnews.upenn.edu!msuinfo!convex.cl.msu.edu!boone
- From: boone@convex.cl.msu.edu (Dennis Boone)
- Newsgroups: alt.gopher
- Subject: Re: .cache
- Message-ID: <1992Aug17.221508.12934@msuinfo.cl.msu.edu>
- Date: 17 Aug 92 22:15:08 GMT
- References: <1992Aug12.195021.8790@trentu.ca> <5733@m1.cs.man.ac.uk>
- Sender: news@msuinfo.cl.msu.edu
- Organization: Michigan State University, East Lansing
- Lines: 21
-
- In article <5733@m1.cs.man.ac.uk> M.Whidby@mcc.ac.uk writes:
- >Disadvantage - as you noted, if you change something in the tree it doesn't
- >appear immediately as viewed by the client until the cache file expires
- >(10 minutes by default I think). I run with caching on but if I want to
- >check something I've just inserted I do an 'rm .cache' in the appropriate
- >directory. Perhaps soemone should write a script to remove all .cache files
- >in a directory. (I miss the tree-walking capabilities that Primos had in
- >its wildcarding...)
-
- At least they could have chosen more commonly used characters for their
- wildcarding. (Yeah, I know, I know, they were there first.)
-
- Try:
-
- find . -name .cache -exec rm {} ;;
-
- but you'll have to figure out for your shell which of the special characters
- (ie {};) need to be escaped. It should be roughly equivalent to the
- delete *>@@>@@ that you miss.
- --
- == Frustration is portable. ==
-