summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: f6f2aa3)
raw | patch | inline | side by side (parent: f6f2aa3)
author | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 2 May 2007 16:44:44 +0000 (12:44 -0400) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Wed, 2 May 2007 16:44:44 +0000 (12:44 -0400) |
If the path of our wish executable that are running under
contains spaces we need to make sure they are escaped in
a proper Tcl list, otherwise we are unable to start gitk.
Reported by Randal L. Schwartz on #git.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
contains spaces we need to make sure they are escaped in
a proper Tcl list, otherwise we are unable to start gitk.
Reported by Randal L. Schwartz on #git.
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 7cbc977ea29f2d0060476c3973df16c5abf6fe12..ae881336dac0807d1f4a026b649c75febdc1b8b3 100755 (executable)
--- a/git-gui.sh
+++ b/git-gui.sh
# -- Always start gitk through whatever we were loaded with. This
# lets us bypass using shell process on Windows systems.
#
- set cmd [info nameofexecutable]
+ set cmd [list [info nameofexecutable]]
lappend cmd [gitexec gitk]
if {$revs ne {}} {
append cmd { }