summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 183a1d1)
raw | patch | inline | side by side (parent: 183a1d1)
author | Shawn O. Pearce <spearce@spearce.org> | |
Fri, 21 Sep 2007 15:08:50 +0000 (11:08 -0400) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Sat, 22 Sep 2007 01:58:37 +0000 (21:58 -0400) |
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 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 | patch | blob | history |
diff --git a/git-gui.sh b/git-gui.sh
index 10710e26c69a987fe2a712c1c146442525fefc05..62e165227633338cdc8deaede8cfd07ea6ddd804 100755 (executable)
--- a/git-gui.sh
+++ b/git-gui.sh
global env _search_exe _search_path
if {$_search_path eq {}} {
- if {[is_Cygwin]} {
+ if {[is_Cygwin] && [regexp {^(/|\.:)} $env(PATH)]} {
set _search_path [split [exec cygpath \
--windows \
--path \