Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with Paths in Commands #7

Open
pfeilbr opened this issue Nov 22, 2011 · 6 comments
Open

Issues with Paths in Commands #7

pfeilbr opened this issue Nov 22, 2011 · 6 comments

Comments

@pfeilbr
Copy link

pfeilbr commented Nov 22, 2011

All the hard coded references to ~/Library/Application\ Support/TextMate/Bundles/ForceDotBundle.tmbundle in the various commands don't work for me. When you install a bundle in TextMate it puts it in ~/Library/Application Support/TextMate/Pristine Copy/Bundles (http://j.mp/vdQsuB). For example ForceDotBundle gets put in ~/Library/Application Support/TextMate/Pristine Copy/Bundles/ForceDotBundle.tmbundle. The only time ~/Library/Application\ Support/TextMate/Bundles/ForceDotBundle.tmbundle gets created is if you make a change to the bundle in the TextMate bundle editor, and only the differences are stored there. The $TM_BUNDLE_SUPPORT environment variable should be used (http://j.mp/skTHh1).

Thanks for creating this. Very helpful.

@joshbirk
Copy link
Owner

Most welcome! Interesting - so is it the Keychain access, SOQL callout, etc., that fails?

Did you run the move_tools.sh or move_tools.command? That should create the path to TextMate/Bundles/etc/ to hold the support shell and php scripts, even if the rest of the bundle goes into Pristine. I did just earlier today put in a fix since those the mkdir references were off. I'll look at using the env vars from end to end though.

@joshbirk
Copy link
Owner

Should be noted though, that tonight I'm trying to get an update in to get around some of the keychains bugs as well - plus a downloadable zip with a better installer.

@pfeilbr
Copy link
Author

pfeilbr commented Nov 22, 2011

Yes, Keychain access, and SOQL callout failed. I installed by cloning, then double-clicking on move_tools.command in Finder. After that finished I was only left with ~/Library/Application Support/TextMate/Pristine Copy/Bundles/ForceDotBundle.tmbundle, and nothing in ~/Library/Application\ Support/TextMate/Bundles/ForceDotBundle.tmbundle.

I see the new zip has been posted. I'll give that a try.

Thanks for the prompt reply!

@joshbirk
Copy link
Owner

There was a directory name mismatch with move_tools yesterday which should be fixed now, hopefully the new zip will work correctly. Let me know if not and I'll see about a new script.

@joshbirk
Copy link
Owner

And that zip had a typo in the installer it looks like :/ New upload.

@joshbirk
Copy link
Owner

joshbirk commented Dec 2, 2011

OK, next build will remove the Tools directory, replace it with the correct Support directory and possible eliminate the need of the install script completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants