From: Christiaan H. <cmh...@gm...> - 2009-05-25 09:25:18
|
On 25 May 2009, at 11:08 AM, k2...@gm... wrote: > > > On 25.05.2009, at 10:55, Christiaan Hofman wrote: > >> >> On 25 May 2009, at 10:50 AM, k2...@gm... wrote: >> >>> Hello, >>> >>> each time I do a first search when opening a pdf, the ATSserver >>> process runs for many minutes, using 50% of my CPU, before I can get >>> any results. The following searches will work instantaneously >>> though. >>> >>> If I close Skim and then reopen the same document and do the same >>> search, I have to wait another round for ATSserver to finish >>> whatever >>> it is doing (I suppose indexing, but I don't understand why). >>> >>> Is it possible that my ATSserver or my Skim are broken somehow? >>> >>> Cheers, >>> kaz >> >> Probably not. This is probably the spotlight importer at work. Don't >> know how this is triggered and why, Apple doesn't tell us too much >> about the inner workings. >> >> Christiaan >> > > But was there any well-known change, because I'm positive this hasn't > always be like that on Skim? > > I mean, do you have this phenomen when you search a big pdf for the > first time after opening it? If not, then there is problem on my > computer. > > Cheers and thanks for the reply, > kaz The Skim importer in 1.2.1 was trying to import PDF files, this was reverted in 1.2.2 because Apple did not let us reliable do this anyway. And moreover Apple's importer is more efficient because they've got access to private methods. It may well be that the changes of the importer just trigger a re- import whenever you first open a PDF after the change (or after the system noted that the importer had changed). As I said, I don't know exactly what triggers it. If you want to know which importer your system is using, you can type the following on a single line in Terminal.app: mdimport -d 1 -n /path/to/a/file.pdf Christiaan |