aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexander Gavrilov <angavrilov@gmail.com>2008-12-01 20:30:09 +0300
committerPaul Mackerras <paulus@samba.org>2008-12-02 09:43:12 +1100
commitf3413079d6a0d3d3cbeb506e81e647772b857f81 (patch)
tree4effde2fbab6e651ef992eb3072aedc54257d341
parenta8833ef5404a07983d8eed0a9582c2e19e437b78 (diff)
downloadgit-f3413079d6a0d3d3cbeb506e81e647772b857f81.tar.gz
git-f3413079d6a0d3d3cbeb506e81e647772b857f81.tar.xz
gitk: Make line origin search update the busy status
Currently the 'show origin of this line' feature does not update the status field of the gitk window, so it is not evident that any processing is going on. It may seem at first that clicking the item had no effect. This commit adds calls to set and clear the busy status with an appropriate title, similar to other search commands. Signed-off-by: Alexander Gavrilov <angavrilov@gmail.com> Signed-off-by: Paul Mackerras <paulus@samba.org>
-rwxr-xr-xgitk3
1 files changed, 3 insertions, 0 deletions
diff --git a/gitk b/gitk
index b7447f91c..b8b5e8092 100755
--- a/gitk
+++ b/gitk
@@ -3402,6 +3402,7 @@ proc show_line_source {} {
error_popup [mc "Couldn't start git blame: %s" $err]
return
}
+ nowbusy blaming [mc "Searching"]
fconfigure $f -blocking 0
set i [reg_instance $f]
set blamestuff($i) {}
@@ -3415,6 +3416,7 @@ proc stopblaming {} {
if {[info exists blameinst]} {
stop_instance $blameinst
unset blameinst
+ notbusy blaming
}
}
@@ -3429,6 +3431,7 @@ proc read_line_source {fd inst} {
}
unset commfd($inst)
unset blameinst
+ notbusy blaming
fconfigure $fd -blocking 1
if {[catch {close $fd} err]} {
error_popup [mc "Error running git blame: %s" $err]