From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eros.uknet.ac.uk ([192.91.199.2]) by archone.tamu.edu with SMTP id <45329>; Sun, 9 Feb 1992 12:58:36 -0600 Received: from ibmpcug.co.uk by eros.uknet.ac.uk with UUCP id <18897-0@eros.uknet.ac.uk>; Sun, 9 Feb 1992 18:59:09 +0000 Received: by ibmpcug.co.uk (smail2.5) id AA05996; 9 Feb 92 18:55:48 GMT (Sun) X-Phone-Work: +44 81 863-1191 X-Fax-Work: +44 81 863-6095 X-Favourite-Colour: black, of course. In-Reply-To: <199202081101.AA05781@cerberus.bhpese.oz.au> Organization: The IBM PC User Group, UK. X-Mailer: Mail User's Shell (7.1.2 7/11/90) To: rc@archone.tamu.edu Subject: Re: path caching Message-Id: <9202091855.AA05991@ibmpcug.co.uk> Date: Sun, 9 Feb 1992 12:55:47 -0600 From: Matthew Farwell In article <199202081101.AA05781@cerberus.bhpese.oz.au> you write: >I've been playing with the idea of a file system based path cache, as >my path is rather long. Enclosed is some doco I wrote on the caching, >and accompanying instrumentation. This is currently for rc 1.2, I am >just about to post it to 1.3b. Comments ? > >[ deleted ] Why can't you do something like: This is untested, since I don't have symbolic links. cache = $home/.cache fn rehash { for (i in $path) { @{ cd $i for (j in *) { if (! test -x $cache/$j) ln -s $i/$j $cache/$j } } } } or something like that. Then you only require one directory in your path, ie $cache. Dylan.