Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • those ._ files are (I think) your mac saving the resource forks for the files. On an HFS volume, those would be stored in the resource fork of the file. On non-HFS volumes, the mac creates a ._ file in which to store the resource fork. You'll typically encounter this when your mac has mounted some PC or Unix volume, or when you've formated some partition as UFS or something.

    You can delete them immediately before packaging for distribution (or incorporate that into your packaging script). Another option wou
    • ...ooops

      I'm reading from my "amigos" page which showed your earlier journal entry, but further down a ways and so I see now that you already know the cause.

      never mind :)

    • Thanks for the reply anyway... have you experienced any problems with deletion of the resource files?

      hyperstation ~/Develop/Copenhagen/modules/Games/Bingo/Bot % find . -name "._*"

      hyperstation ~/Develop/Copenhagen/modules/Games/Bingo/Bot % rm -Rf ._*

      hyperstation ~/Develop/Copenhagen/modules/Games/Bingo/Bot % find . -name "._*"

      hyperstation ~/Develop/Copenhagen/modules/Games/Bi

      • > any problems with deletion of the resource files?


        The sorts of things you might be likely to drop when working with text files include type/creator (which would go back to their default according to file extension and your OS prefs... 'get info' on a file and 'change all files of this type' to change your OS prefs) and editor nicities window size/placement and cursor/selection loction when last saved.

        If you don't mind missing those sorts of details, then deleting the resource forks of text files