Allan Odgaard wrote ..
I know this isn't optimal, but I have no idea on how I can handle this problem gracefully.
How about implementing:
TM_BUNDLE_USER_PATH TM_BUNDLE_SYSTEM_PATH TM_BUNDLE_NETWORK_PATH
to point to their obvious locations. Then, at least scripts can access each of the bundles easily and by using TextMate's search order, can allow users to override items the normal way. Obviously, TextMate should only set a variable if the relevant bundle is actually at the location.
Best, Erich
On 07/05/2005, at 8.26, subscriber@ampede.com wrote:
Allan Odgaard wrote ..
I know this isn't optimal, but I have no idea on how I can handle this problem gracefully.
How about implementing: TM_BUNDLE_USER_PATH TM_BUNDLE_SYSTEM_PATH TM_BUNDLE_NETWORK_PATH
Or how about adding those directories to the default search path before commands are executed, e.g. by putting them in the PATH env- var? In that way scripts would be able to execute automatically. They should probably be added to the beginning.
On May 7, 2005, at 11:51, Sune Foldager wrote:
How about implementing: TM_BUNDLE_USER_PATH TM_BUNDLE_SYSTEM_PATH TM_BUNDLE_NETWORK_PATH
Or how about adding those directories to the default search path before commands are executed, e.g. by putting them in the PATH env-var? In that way scripts would be able to execute automatically. They should probably be added to the beginning.
In several cases the additional resources placed in the bundles are style sheets (for commands with HTML output), samples (for e.g. the obj-c build command), documents (for documentation) etc. -- so adding to the PATH wouldn't help much.
Having a variable per location wouldn't help either, e.g. with 1.1b5 most bundles came included in the TM app, for b5-8 my suggestion has been to do the svn checkout in /Library, but bundle contributers most likely will have it in ~/Library. So if the command really knew which of these places it was installed, it could probably just use (~|/System)?/Library instead of the bundle path.