Closed GoogleCodeExporter closed 8 years ago
[deleted comment]
UPDATE:
I can now open and use OpenInGitGUI-2.0 (not sure what I did, but it works
now), but
I can't use pull, clone, fetch or do anything that involves data being
downloaded to
me when using it. I get a "fatal: the remote end hung up unexpectedly" error.
They
work fine in the Terminal though, and pushing through the GUI works most of the
time.
I have reset my SSH keys and my Known Hosts list locally and with my online
repository hosts, but that hasn't helped. Neither has disabling my firewall or
anti-virus.
I have also discovered that when there is no Known Hosts and Wish asks you if
you
want to add a host, typing "yes" in the text box and pressing OK causes Wish to
stop
responding (or take longer than 20 minutes to do something).
I don't know for sure where the problems lie, but some helpful advice would be
appreciated.
Regards,
- Steve
Original comment by stevenbl...@googlemail.com
on 14 Jan 2009 at 10:36
i definitely know what your talking about. i had to wrap git gui in a screen
session to overcome the
problems with ssh downloading as youve described.
does git gui work from the terminal?
can you connect to the screen session git gui is running under ("screen -r"
from the terminal)?
i have verified that this works on at least 2 machines. something sounds fishy.
Original comment by timchar...@gmail.com
on 14 Jan 2009 at 12:02
i definitely know what your talking about. i had to wrap git gui in a screen
session to overcome the
problems with ssh downloading as youve described.
does git gui work from the terminal?
can you connect to the screen session git gui is running under ("screen -r"
from the terminal)?
i have verified that this works on at least 2 machines. something sounds fishy.
Original comment by timchar...@gmail.com
on 14 Jan 2009 at 12:02
I can open Git GUI through Terminal using "git gui screen -r". Clicking on any
of the
links in the GUI gives me "usage: /usr/local/git/libexec/git-core/git-gui
[{blame|browser|citool}]" in the Terminal.
Using "screen -r" on it's own tells me "there is no screen to be resumed".
Original comment by stevenbl...@googlemail.com
on 14 Jan 2009 at 2:25
SUCCESS!
I think I have found the problem!
MacGit does not seem to like folder paths with whitespace in their names.
As I am an avid World of WarCraft (WoW) player and addon author, I like to have
my
repositories in the directory where WoW recognises addons so I can test and
commit/push changes from where they are used.
The path is:
/Applications/World of WarCraft/Interface/AddOns/
(that's the default install path for WoW).
I can push, pull, clone etc when I move my repositories to the Applications
folder. I
guess names-with-whitespace support was lost/removed with the move away from
using
two Terminal windows to open Git GUI.
I hope this information is of use to you.
Regards,
- Steve
Original comment by stevenbl...@googlemail.com
on 16 Jan 2009 at 7:50
That's very good to know. The git gui script probably needs to be modified to
handle
escape paths with spaces then. This is a late response... but hey, you get to
things
when you can :)
Original comment by timchar...@gmail.com
on 12 Jun 2009 at 4:54
Original comment by timchar...@gmail.com
on 9 Dec 2010 at 10:53
Version 2.1 contains the fix
Original comment by timchar...@gmail.com
on 9 Dec 2010 at 10:53
Original issue reported on code.google.com by
stevenbl...@googlemail.com
on 12 Jan 2009 at 11:19