From: Martin Waitz <tali@admingilde.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: exception in git-gui when saving options
Date: Sat, 17 Feb 2007 20:40:33 +0100 [thread overview]
Message-ID: <20070217194033.GH21842@admingilde.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
hoi :)
I get the following backtrace when I want to save options in a
git-gui which is started in blame mode:
can't read "current_diff_path": no such variable
while executing
"set p $current_diff_path"
(procedure "reshow_diff" line 5)
invoked from within
"reshow_diff"
(procedure "do_save_config" line 5)
invoked from within
"do_save_config .options_editor"
invoked from within
".options_editor.buttons.save invoke"
("uplevel" body line 1)
invoked from within
"uplevel #0 [list $w invoke]"
(procedure "tk::ButtonUp" line 22)
invoked from within
"tk::ButtonUp .options_editor.buttons.save"
(command bound to event)
The options seem to be saved correctly.
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-02-17 19:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 19:40 Martin Waitz [this message]
2007-02-18 7:14 ` exception in git-gui when saving options Shawn O. Pearce
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=20070217194033.GH21842@admingilde.org \
--to=tali@admingilde.org \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).