| commit | 299077fb40eac1e128b7bc09d5d992960e6f11c2 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Fri, 21 Sep 2007 15:08:50 +0000 (21 11:08 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sat, 22 Sep 2007 01:58:37 +0000 (21 21:58 -0400) | ||
| tree | 30c124a00ce874c3855ed391989558a44553d175 | treesnapshot (tar.gz zip) |
| parent | 183a1d1496921e16d316ac523146385af39fcdb0 | commitdiff |
git-gui: Handle starting on mapped shares under Cygwin
I really cannot explain Cygwin's behavior here but if we start
git-gui through Cygwin on a local drive it appears that Cygwin
is leaving $env(PATH) in Unix style, even if it started a native
(non-Cygwin) Tcl/Tk process to run git-gui. Yet starting that
same git-gui and Tcl/Tk combination through Cygwin on a network
share causes it to automatically convert $env(PATH) into Windows
style, which broke our internal "which" implementation.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
I really cannot explain Cygwin's behavior here but if we start
git-gui through Cygwin on a local drive it appears that Cygwin
is leaving $env(PATH) in Unix style, even if it started a native
(non-Cygwin) Tcl/Tk process to run git-gui. Yet starting that
same git-gui and Tcl/Tk combination through Cygwin on a network
share causes it to automatically convert $env(PATH) into Windows
style, which broke our internal "which" implementation.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| git-gui.sh | diffblobblamehistory |