TGit 1.8.11 is not using %HOME% correctly
By neil.bry... on September 01, 2014 20:19 (imported from Google Code)
What steps will reproduce the problem?
- Launch a command from the Explorer Context Menu
What is the expected output? What do you see instead?
Prior to the upgrade, everything worked.
With 1.8.11.0, I get some variation of an error message ending with: unable to access 'P:/.gitconfig': Invalid argment
What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGit 1.8.11.0
git version 1.9.4.msysgit.1
Please provide any additional information below.
I've been using TortoiseGit on this machine all year, with no incidents. Yesterday, it prompted to upgrade to 1.8.11.0, which I allowed. After the upgrade, I get error boxes if I try to commit, etc (using the menu from an explorer window under C:\Users\Me...):
Git Commit -> 'master'...
Could not get parent from HEAD.
libgit reports:
unable to access 'H:/.gitconfig': Invalid argment
TortoiseGit | Show Log
Could not initialize libgit.
libgit reports:
unable to access 'H:/.gitconfig': Invalid argment
I've made sure msysgit is upgraded (was git version 1.9.4.msysgit.0 upgraded to git version 1.9.4.msysgit.1), with no change in behavior.
H: is my %HOMEDRIVE%%HOMEPATH% value, as assigned by company policy, but it is not my %HOME% value:
HOME=C:\Users\Me
HOMEDRIVE=H:
HOMEPATH=\
HOMESHARE=\SERVER\SHARE\Me
No other environment variable has any reference to H:.
I've looked through the settings and config files that I could find and could not find a reference to H:, %HOMEDRIVE%, or '~'. None of the config files listed in the TG Settings | git pane have any such reference.
I'd be happy to just override this, if I could figure out where. %HOME% is set from the previous version (don't remember which it was, but should have been current), and that was what I had anticipated the fix would be. AFAIK, that is the most likely variable(?) for this type of issue.
I changed the directory for the user command prompt shortcut from %HOMEDRIVE%%HOMESHARE% to %HOME%, on the chance that TG was shelling out, changing directories, and the different drives were breaking that, but it had no effect.
I am getting around this by using the git menus--no problems there--but the issue is effectively disabling TG.
As a sidebar, looking through the trouble tickets for this, I see a few references to TG hanging when you click a command. This is also happening to me, as I suspect it is trying to poll what is essentially a disconnected drive. It did not hang on the previous version that I can remember.