SCM HUD Troubleshooting

From ChangesWiki

SCM HUD Troubleshooting

These instructions apply to the TextMate, BBEdit, TextWrangler, Coda, and Espresso SCM HUD integration features.

Occasionally, the SCM HUD has issues finding the correct path for your SCM terminal utility, or your SCM terminal utility is too old (earlier versions) to be used with the SCM HUD.

1. Does the SCM HUD feature support your SCM flavor?
   • The SCM HUD currently supports Subversion (svn), Mercurial (hg), and Git (git), to add your own script, look here: SCM_Adapter_Scripts
2. Is the SCM HUD is able to find your SCM terminal utility (svn, git, or hg)?
   • find the path to your default SCM terminal utility by using the following applicable command at the Terminal:
     which svn (for svn)
     which hg (for hg)
     which git (for git)
     
   • for svn - set the CHNG_SVN environment variable for your login session to point to your SCM terminal utility (i.e. /opt/subversion/bin/svn)
   • for hg - set the CHNG_HG environment variable for your login session to point to your SCM terminal utility (i.e. /usr/local/hg/bin/hg)
   • for git - set the CHNG_GIT environment variable for your login session to point to your SCM terminal utility (i.e. /usr/local/git/bin/git)
   • to set your environment variables, goto Changes -> Preferences and then choose the Advanced tab. Add your environment variable name and value to the table below.
     
     
3. Is your SCM terminal utility too old to be used with the SVN HUD?
   • There is a known issue with versions of git older than version 1.6.2.1. Download and install a newer version of git from: http://code.google.com/p/git-osx-installer/
4. Is your SCM terminal utility too old to work with your repository?
   • Older versions of the Subversion terminal utility will not work with newer repositories in some cases. Test for compatibility outside of Changes.