fane_j wrote:
Environment.plist is not for testing.
I never said it was. I said DYLD_INSERT_LIBRARIES is for testing. Environment.plist is for lazy programmers.
If environment.plist is a hack, then it is a hack designed by Apple, made by Apple, supported by Apple, and indicated to developers by Apple (see the two developer library docs I referred above). You'll forgive me if, between Apple's recommandation and yours, I go with Apple's.
There is a great deal in Apple's example code, documentation, and in the operating system itself that should not be used in production code. A competent, professional developer will know which ones those are.
Please explain that to Apple. They've been providing and supporting the wrong answer for, what is it now? Over 10 years? Since v10.0 or thereabouts?
I'm sorry, but if you don't get it then you just don't get it. I can't do any more to explain it. I don't even rely on environment variables when I'm writing pure command-line scripts on Linux. If I have 3rd party software that does require them, I set them up in my own, controlled environment using resource files and then kick off the third party tools in the properly setup environment. I would never stick a file in a user's home directory for that.
With great respect, I'm not about to consider that your configuration is the proper measure for all Mac OS X users. Between Apple and BareBones (who've been developing Mac software for over twenty years now) on one side, and you on the other side, with regret, I'll have to choose the former.
BBEdit only uses that file to run scripts from the GUI. I'm quite sure that it isn't required. People using BBEdit probably know how to deal with that file. If it gets blown away, they can easily restore it. (And, for the record, I've been developing Mac software for 25 years now).