Re: Sherlock and my Sad Source Search Story
Re: Sherlock and my Sad Source Search Story
- Subject: Re: Sherlock and my Sad Source Search Story
- From: Andreas Monitzer <email@hidden>
- Date: Thu, 9 Aug 2001 17:40:51 +0200
On Thursday, August 9, 2001, at 05:21 , Chilton Webb wrote:
Puzzled, I opened the 'old' version of Sherlock 2, under Classic. It
first warned me that this version was not optimized to run under OSX. OK,
so it'll run slower. So I searched. FOUR copies of the source code file
popped up, almost instantly. So I did a quick little benchmark of another
file which was *sitting on my desktop*.
Sherlock/OSX
18.80 seconds
>> no matches <<
Sherlock/Classic
15.26 seconds
7 matches including the one on the desktop
So I thought I'd mention this to other developers who are having problems
finding files on your drive. I assume the optimization of Sherlock
included support for UFS drives, so the old sherlock isn't your best bet
for those types of drives. But if you're searching for source code on an
extended format drives, Classic may be your friend.
I'm always using "find" for file searches. During the launch and thinking
period of Sherlock I've got a hundred matches in Terminal.
find <dir> -name <pattern>
for example:
find . -name \*.m
Search for ObjC-files beginning in the current directory.
find . -name \*AM\*
Search for all files whose name contains "AM".
find .
List all files in the current directory including sub-dirs.
It's not optimized for HFS+, but my home is on an UFS-drive anyways and it'
s much faster than using Sherlock even on HFS+.
andy
--
Discussion forthcoming.