Re: [Boston.pm] OS-X and apple filesystem mapping ?
On 18/03/2003 at 19:08 -0500, Federico Lucifredi wrote: I recall one of the Perl Mongers (perhaps Uri?) mentioning an article on how the apple designers had to bend over backwards to implement the mac's filesystem conventions on a UNIX filesystem. http://www.mit.edu/people/wsanchez/papers/USENIX_2000/ As I recently noted the swamp of dot-something files that OS-X hides on my zip disks, I would be interested in being pointed to such article so that I can at least know what that swamp of files is for. They're Finder window positioning data, mainly; this is what .DS_Store is, anyway. -- :: paul :: complies with canandian cs1471 protocol ___ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
Re: [Boston.pm] file types in Mac OS X
On 02/02/2003 at 13:33 -0500, Beth Chaplin wrote: I have written a perl script that runs on my OS X system (through the terminal), and produces a text output file that is meant to be later read by a Mac application (Filemaker Pro, which imports the data from the file into a database). The problem: When Perl creates the text file, it does not get assigned the proper 'file type'. Instead of being recognizable by the Mac system as a text file, it has the file type '', and most Mac applications do not recognize it. Is there any way in perl (or UNIX) to change the file type of a newly created file without having to do it manually through the Mac GUI? I get the feeling that this problem has something to do with the unique way the Mac system assigns file types. I assume you have the Developer Tools installed. These install a pair of tools called SetFile and GetFile Info: blech@piezo:~$ /Developer/Tools/SetFile --help Usage: SetFile [option...] file... -c creator# file creator -t type # file type (Edited for space. There are many more options.) For example, "/Developer/Tools/SetFile -t 'TEXT' -c 'R*ch' new.txt" will make BBEdit the default application for opening the text file "new.txt". However, under Mac OS X, you should also be able to get away with merely setting a text extension. For a full description of how double-clicking a file chooses which application handles it, you'll want to examine the Launch Services documentation: http://developer.apple.com/technotes/tn/tn2017.html You might also want to look at the [EMAIL PROTECTED] mailing list: http://lists.perl.org/showlist.cgi?name=macosx Cheers, -- :: paul :: we're like crystal ___ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
Re: [Boston.pm] OT: Favorite Mac OS X utilities
On 03/01/2003 at 16:39 -0500, David H. Adler wrote: On Fri, Jan 03, 2003 at 03:51:14PM -0500, Drew Taylor wrote: I just ran across an Eudora importer for Mail.app on version tracker yesterday. "Eudora Mailbox Cleaner - 1-step migration from Eudora to Mail.app" http://www.versiontracker.com/moreinfo.fcgi?id=13341=mac I'm actually not being overly thrilled with Mail.app, and am thinking of going the other way, but I don't see anything that goes in that direction, conversion-wise. :-/ As long as you can find the mboxes, and convert them to have Macintosh line breaks, then Eudora should be able to import them without trouble. I tested this by taking ~/Library/Mail/Mailboxes/Sent Messages.mbox/mbox, saving it as a text file with Macintosh line breaks, and loading it with the Mailbox>Other command in Eudora 5.2, and it worked fine, albeit losing the read flags. If this is important to you, you'd have to do some coding, I expect, possibly by parsing the table_of_contents in the mbox folder. (Eudora has the benefit that I expect I'm alone in finding useful of working in Mac OS as well as Mac OS X.) -- :: paul :: we're like crystal ___ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
Re: [Boston.pm] OT: Favorite Mac OS X utilities
On 03/01/2003 at 22:58 -0500, Peter R. Wood wrote: The general sequence of events was: Apple releases original Sherlock; Actually, the original Sherlock was version 1 for Mac OS 8.5, which was a slightly beefed up (and genuinely usable) version of the old Find File app. Then OS 9 (*) introduced Sherlock 2, which was utterly useless as far as I was concerned, as it put things that never should have been there in the application, and made its primary purpose (finding local files) a pain to use. Thankfully, in OS 9 you could use Sherlock 1 as a front end to the newer Find By Content libraries. Sadly, in OS X Sherlock 2 was the only game in town, which is another of the many reasons I never got on with OS X before Jaguar. Sensibly 10.2 seperates back out the local file searching, so I never have to touch either Sherlock or Watson; both so US-centric to be irrelevant to the other 95% of the world's population. -- :: paul :: we're like crystal ___ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
