summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShawn O. Pearce <spearce@spearce.org>2007-02-11 22:19:38 (GMT)
committerShawn O. Pearce <spearce@spearce.org>2007-02-11 22:19:38 (GMT)
commit0960f7d6db89fa8418486cd088759e54dd51d54e (patch)
tree375f9034222d967ff22fdb186d1af75c753530f0
parentd585e782b0bfb11173028091cb11c8459766135c (diff)
downloadgit-0960f7d6db89fa8418486cd088759e54dd51d54e.zip
git-0960f7d6db89fa8418486cd088759e54dd51d54e.tar.gz
git-0960f7d6db89fa8418486cd088759e54dd51d54e.tar.bz2
git-gui: Stop deleting gitk preferences.
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>
-rwxr-xr-xgit-gui.sh8
1 files changed, 0 insertions, 8 deletions
diff --git a/git-gui.sh b/git-gui.sh
index f44e549..ea16be4 100755
--- a/git-gui.sh
+++ b/git-gui.sh
@@ -4015,14 +4015,6 @@ set starting_gitk_msg {Starting gitk... please wait...}
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.
#