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

git: command not found #4

Open
shadowhand opened this issue Mar 31, 2010 · 5 comments
Open

git: command not found #4

shadowhand opened this issue Mar 31, 2010 · 5 comments

Comments

@shadowhand
Copy link

Github.tmbundle should use the TextMate TM_GIT variable to determine the path to git rather than assuming git is within $PATH.

@adamn
Copy link

adamn commented Apr 6, 2010

I'm getting this error and TM_GIT is set and git is in one of the $PATH directories and the git bundle works.

@shadowhand
Copy link
Author

If you look at the source of Github.tmbundle, you will see that the TM_GIT variable is never used. As for $PATH, I assume that TextMate can only read the global paths, not the ones defined in your shell, so even if you see git in Terminal, it doesn't mean that TextMate knows where it is.

@ats
Copy link

ats commented May 2, 2010

I modified gist.rb in the Support/lib directory to use TM_GIT, as in this gist snippet: http://gist.github.com/387222. Appears to have done the trick for me.

@alanhogan
Copy link

ats, that fix does not seem to solve this problem for me (I reloaded bundles and got the same error). Maybe I did something wrong.

@ats
Copy link

ats commented Aug 27, 2010

alan, did you add TM_GIT with the path to your git binary (mine is /usr/local/bin/git) to preferences -> advanced -> shell variables? I don't know what the exact problem is, but I just couldn't get TextMate to find git via my path, so I added the in-TM shell variable to the command line.

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

4 participants