From: Seth Falcon <sethfalcon@gmail.com>
To: Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: gitk broken or user error?
Date: Mon, 13 Nov 2006 14:28:07 -0800 [thread overview]
Message-ID: <m27ixzgex4.fsf@ziti.local> (raw)
In-Reply-To: <17752.60467.854884.206737@cargo.ozlabs.ibm.com> (Paul Mackerras's message of "Tue, 14 Nov 2006 09:05:39 +1100")
Paul Mackerras <paulus@samba.org> writes:
> Those lines are intended to enable the "Edit view" and "Delete view"
> entries in the View menu. Those entries start out disabled and are
> supposed to be disabled when the "All files" view is displayed, and
> enabled when any other view is displayed.
>
> I suspect that under OSX, the menu gets an extra entry, or something,
> that throws off the numbering. Instead of commenting out those lines,
> could you instead try changing the 2 and 3 to "Edit*" and "Delete*"
> instead? If that works I'll do a patch to fix the problem properly.
I tried this patch:
diff --git a/gitk b/gitk
index ab383b3..e7ea4e2 100755
--- a/gitk
+++ b/gitk
@@ -6305,8 +6305,8 @@ if {$cmdline_files ne {} || $revtreeargs
set viewargs(1) $revtreeargs
set viewperm(1) 0
addviewmenu 1
- .bar.view entryconf 2 -state normal
- .bar.view entryconf 3 -state normal
+ .bar.view entryconf "Edit*" -state normal
+ .bar.view entryconf "Delete*" -state normal
}
if {[info exists permviews]} {
And, yes, this allows gitk to load up and be useful. So this is much
better than the current behavior. However, if I try clicking on the
"All files" view in the view menu, I get an error box along these
lines:
unknown option "-state"
unknown option "-state"
while executing
".bar.view entryconf 3 -state [expr {$n == 0? "disabled": "normal"}]"
(procedure "showview" line 56)
invoked from within
"showview 0"
(menu invoke)
Perhaps a similar fix is needed in other parts of the code.
+ seth
next prev parent reply other threads:[~2006-11-13 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 17:00 gitk broken or user error? Seth Falcon
2006-11-13 5:20 ` Shawn Pearce
2006-11-13 22:05 ` Paul Mackerras
2006-11-13 22:28 ` Seth Falcon [this message]
2006-11-13 22:38 ` Seth Falcon
2006-11-13 22:42 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m27ixzgex4.fsf@ziti.local \
--to=sethfalcon@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.