~/scwork/ExtensionsJust a suggestion. Since scwork already contains customized info, it could help keep personal user things all in one place (rather than ~/Library/Application Support).
Just an idea. Josh ****************************************** Joshua D. Parmenter Graduate Student, Music Composition http://students.washington.edu/joshp"...Some people think a composer's supposed to please them, but in a way a composer is a chronicler... He's supposed to report on what he's seen and lived." -Charles Mingus
Josh Parmenter wrote:
Thanks for the directions. It seems to work really well! Josh ****************************************** Joshua D. Parmenter Graduate Student, Music Composition http://students.washington.edu/joshp"...Some people think a composer's supposed to please them, but in a way a composer is a chronicler... He's supposed to report on what he's seen and lived." -Charles MingusRohan Drape wrote:Pardon my ignorance, but how do I run the patch to try it out?Actually I really ought to have given proper instructions.From the root of the SuperCollider tree type:$ patch -p1 < PATCH_FILE where PATCH_FILE is the patch to be applied. To revert the patch, if you don't like it, type: $ patch -R -p1 < PATCH_FILE For details on how the -p option works type: $ man patch Using -p1 is standard lkml practice... Regards, Rohan PS. If a patch is compressed type: $ bzcat PATCH_FILE | patch -p1 _______________________________________________ sc-dev mailing list sc-dev@xxxxxxxxxxxxxxx http://www.create.ucsb.edu/mailman/listinfo/sc-dev_______________________________________________ sc-dev mailing list sc-dev@xxxxxxxxxxxxxxx http://www.create.ucsb.edu/mailman/listinfo/sc-dev