git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "David Tweed" <david.tweed@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: "freezing" gitk geometry
Date: Wed, 14 Feb 2007 09:53:26 -0800	[thread overview]
Message-ID: <7vsld8pqw9.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <e1dab3980702140923m1e4e430ci28f8ed246c5fe786@mail.gmail.com> (David Tweed's message of "Wed, 14 Feb 2007 17:23:51 +0000")

"David Tweed" <david.tweed@gmail.com> writes:

> now I've installed 1.5.0, I've discovered gitk is still the
> visualisation tool for graphically browsing history. I think gitk is a
> good program, but one thing I'd like to be able to change is to have a
> way to force gitk not to update its saved internal geometry (position
> of internal dividers, etc) when it exits. I tried making ~/.gitk not
> writable but that didn't work. I don't know tcl: is there a simple way
> to prevent gitk updating this upon quitting?

I do not talk Tcl, but I think you can apply this patch and then
if you add

	set dontsave 1

at the end of ~/.gitk with your editor, it would stop updating
your geometry (or anything else for that matter).

diff --git a/gitk b/gitk
index 9ddff3e..cd0d68d 100755
--- a/gitk
+++ b/gitk
@@ -813,9 +813,10 @@ proc savestuff {w} {
     global maxwidth showneartags
     global viewname viewfiles viewargs viewperm nextviewnum
     global cmitmode wrapcomment
-    global colors bgcolor fgcolor diffcolors
+    global colors bgcolor fgcolor diffcolors dontsave
 
     if {$stuffsaved} return
+    if {$dontsave} return
     if {![winfo viewable .]} return
     catch {
 	set f [open "~/.gitk-new" w]
@@ -6251,6 +6252,7 @@ set bgcolor white
 set fgcolor black
 set diffcolors {red "#00a000" blue}
 
+set dontsave 0
 catch {source ~/.gitk}
 
 font create optionfont -family sans-serif -size -12

      reply	other threads:[~2007-02-14 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 17:23 "freezing" gitk geometry David Tweed
2007-02-14 17:53 ` Junio C Hamano [this message]

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=7vsld8pqw9.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=david.tweed@gmail.com \
    --cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).