summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: d585e78)
raw | patch | inline | side by side (parent: d585e78)
author | Shawn O. Pearce <spearce@spearce.org> | |
Sun, 11 Feb 2007 22:19:38 +0000 (17:19 -0500) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Sun, 11 Feb 2007 22:19:38 +0000 (17:19 -0500) |
Now that git 1.5.0 and later contains a version of gitk that uses
correct geometry on Windows platforms, even if ~/.gitk exists, we
should not delete the user's ~/.gitk to work around the bug. It
is downright mean to remove a user's preferences for another app.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
correct geometry on Windows platforms, even if ~/.gitk exists, we
should not delete the user's ~/.gitk to work around the bug. It
is downright mean to remove a user's preferences for another app.
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 f44e5490991aa95ef92b8939993abe751e8e0f2d..ea16be43ac900d3946ddf01107ed46493029169b 100755 (executable)
--- a/git-gui.sh
+++ b/git-gui.sh
proc do_gitk {revs} {
global env ui_status_value starting_gitk_msg
- # -- On Windows gitk is severly broken, and right now it seems like
- # nobody cares about fixing it. The only known workaround is to
- # always delete ~/.gitk before starting the program.
- #
- if {[is_Windows]} {
- catch {file delete [file join $env(HOME) .gitk]}
- }
-
# -- Always start gitk through whatever we were loaded with. This
# lets us bypass using shell process on Windows systems.
#