On Mar 21, 2005, at 3:18 PM, Lola Lee wrote:
It really does make it easier on my eyes, at least. :-) BTW, came across a bug that caused the app to crash when I tried to set up my own profile to access the 5.8.6 docs; will send you the details later.
Please do.
Meanwhile, the simplest way to set up a DocSet for a perl that will run on your system is to let ShuX itself figure out all the correct paths. In Preferences, just click the "Perl..." button under the DocSet popup. You'll get a selection sheet where you can choose the directory where a "perl" binary lives. ShuX will then run the chosen Perl to figure out where it stores its pods and modules.
The other way, clicking the "Add" button and filling in the paths manually, is intended for cases where the Perl for which you want to add a DocSet isn't installed on your current system. For example, you might have Tiger installed on another volume, and you might want to add a DocSet for browsing Tiger's Perl docs while you're booted into Panther. You might not be able to run the Tiger Perl under the OS you're booted into, and even if you *could* run it, the Tiger volume is mounted as / when it's the boot volume and under /Volumes when it's not, so the paths returned by the Tiger Perl aren't likely to be valid if you're booted into Panther anyway.
Like I said though - please do send me the crash log, the paths you entered for the DocSet, and any other relevant info you can think of. Entering invalid paths in a DocSet should cause ShuX to complain about them, not just give up and crash.
sherm--
Cocoa programming in Perl: http://camelbones.sourceforge.net Hire me! My resume: http://www.dot-app.org