Re: Tiger documentation update
Re: Tiger documentation update
- Subject: Re: Tiger documentation update
- From: kevin callahan <email@hidden>
- Date: Sun, 8 May 2005 11:17:31 -0700
On May 8, 2005, at 10:59 AM, Charles Srstka wrote:
You're gonna love this - Spotlight is hard-wired to ignore the /
Developer/ADC Reference Library folder when indexing. It will not
get indexed, and you will not be able to content-search it at *all*
using Spotlight. Apple has apparently assumed that the XCode doc
search is good enough and you would never, ever need to use
Spotlight to search the developer docs. Isn't that great?
I put an alias to the ADC Reference Library in my ~/Documents folder,
and when I do a Spotlight search, I get results back from /Developer/..
Kevin
Workarounds? Sure, you can use mdimport -f to force /Developer/ADC
Reference Library to get indexed. And when you do so, you'll be
able to content-search the docs as long as you use the Spotlight
menu or search from a location outside /Developer/ADC Reference
Library - i.e. from /Developer or from the root of the drive.
However, if you search from /Developer/ADC Reference Library or a
subfolder of it like /Developer/ADC Reference Library/documentation/
Cocoa, the Finder goes "whoops! This is a folder I'm not supposed
to search!" and bails out without even trying.
Yes, this behavior is *hard-coded* into Spotlight - you can see for
yourself by looking at /System/Library/Frameworks/
CoreServices.framework/Frameworks/Metadata.framework/Versions/A/
Support/mds with a hex editor and searching for "ADC Reference
Library". You'll find it in there. Altering the name slightly and
rebooting causes the folder to become content-searchable all of a
sudden (I tried it).
Fortunately, there seems to be a more elegant way to override this
- in the hidden /.Spotlight-V100 folder, there's a file called
_rules.plist. Editing it to look like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
<plist version="1.0">
<dict>
<key>EXCLUDE</key>
<array/>
<key>INCLUDE</key>
<array>
<string>/Developer/ADC Reference Library</string>
</array>
<key>NOTE</key>
<string>Specify paths to include or exclude, preceeding rules
which target user-homes with ~/</string>
</dict>
</plist>
and then running this command after rebooting:
mdimport /Developer/ADC\ Reference\ Library
should cause the developer docs to be searchable.
Charles
On May 7, 2005, at 12:46 PM, Robert Nicholson wrote:
When you post these updates can you please tell us where the
version information is that enables us to confirm that spotlight
has indexed the new material correctly? For instance if changes
under ADC Reference Library are made I'd still like to be able
confirm that Spotlight indexed everything after the dmg was
installed.
I've got
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
<plist version="1.0">
<dict>
<key>EXCLUDE</key>
<array/>
<key>INCLUDE</key>
<array>
<string>/Developer/ADC Reference Library</string>
</array>
<key>NOTE</key>
<string>Specify paths to include or exclude, preceeding
rules which target user-homes with ~/</string>
</dict>
</plist>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40charlessoft.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden