From: Shawn Pearce <spearce@spearce.org>
To: Seth Falcon <sethfalcon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: gitk broken or user error?
Date: Mon, 13 Nov 2006 00:20:07 -0500 [thread overview]
Message-ID: <20061113052007.GA31551@spearce.org> (raw)
In-Reply-To: <m2irhkr467.fsf@ziti.local>
Seth Falcon <sethfalcon@gmail.com> wrote:
> I get the following error when invoking gitk with any command line
> argument, for example, 'gitk --all':
>
> ziti:~/proj/R-devel seth$ gitk --all
> Error in startup script: unknown option "-state"
> while executing
> ".bar.view entryconf 3 -state normal"
> invoked from within
> "if {$cmdline_files ne {} || $revtreeargs ne {}} {
> # create a view for the files/dirs specified on the command line
> set curview 1
> set selec..."
> (file "/Users/seth/scm/bin/gitk" line 6298)
You are not alone on this. I see the same thing on my Mac and it
makes it quite difficult to use gitk. However the same version of
gitk does not have this problem on Windows. Its clearly related
to platform differences.
Of course Windows is unable to open a gitk window without it
being collapsed down to only the titlebar, and is also unable to
sucessfully reread the user's ~/.gitk file, but that's another bug...
I really should try to figure out what these problems are, but gitk
is 6323 lines of Tcl/Tk code which I'm not all too familiar with,
and I've got my own growing mass of ~2473 lines of Tcl/Tk code in
git-gui to worry about right now...
--
next prev parent reply other threads:[~2006-11-13 5:20 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 [this message]
2006-11-13 22:05 ` Paul Mackerras
2006-11-13 22:28 ` Seth Falcon
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=20061113052007.GA31551@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=sethfalcon@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox