On 30/04/2012, at 08.47, Ron DeVera wrote: > On Sat, Apr 28, 2012 at 4:50 AM, Allan Odgaard <mailingl...@textmate.org> > wrote: >> […] Why do you want to introduce a variable that is effectively an alias for >> TM_PROJECT_DIRECTORY? I.e. wouldn’t it be more clear, and not clutter the >> global namespace, simply to use TM_PROJECT_DIRECTORY in your script? > > The bundle reads an environment variable `TM_OPTIONS_FILE` that other > users can point to a custom path, e.g., `~/.myconfig`, > `$TM_PROJECT_DIRECTORY/config/myconfig.yml`. The custom environment > variable is used not just as an alias, but as an optional part of a > path that can be either global or project-specific.
OK, so users can _optionally_ set this TM_OPTIONS_FILE (in .tm_properties where TM_PROJECT_DIRECTORY is available), right? I.e. your bundle does not require it to be set (by your bundle). Btw: It should preferably be TM_«bundle»_OPTIONS_FILE so to not conflict with variables used by other bundles. _______________________________________________ textmate-dev mailing list textmate-dev@lists.macromates.com http://lists.macromates.com/listinfo/textmate-dev
