From: Junio C Hamano <gitster@pobox.com>
To: Jing Xue <jingxue@digizenstudio.com>
Cc: git <git@vger.kernel.org>
Subject: Re: gitk fails to parse git log output in 1.5.3
Date: Sun, 02 Sep 2007 16:16:05 -0700 [thread overview]
Message-ID: <7vzm04odze.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20070902223128.GA19198@falcon.digizenstudio.com> (Jing Xue's message of "Sun, 2 Sep 2007 18:31:28 -0400")
Jing Xue <jingxue@digizenstudio.com> writes:
> gitk shows an error "Can't parse git log output: {\x1b[33commit..." at
> startup and quits.
>
> Obviously it's because my git-log outputs in color mode. But the same
> happens (and git-log still outputs in colors) after I set color.pager=false.
>
> What am I missing?
This will quickly turn into an FAQ.
Please see:
http://thread.gmane.org/gmane.comp.version-control.git/57204
for details and a possible future plans. Making "diff.color =
true" to always color was a mistake, and if you have such a
configuration, it would break any script that reads from "git
log". In the meantime, do not do "diff.color = true" (or
"color.diff = true") in your configuration; say "auto" instead
of "true", and/or apply this patch.
---
gitk | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/gitk b/gitk
index 300fdce..9c21eff 100755
--- a/gitk
+++ b/gitk
@@ -93,6 +93,7 @@ proc start_rev_list {view} {
}
if {[catch {
set fd [open [concat | git log -z --pretty=raw $order --parents \
+ --no-color \
--boundary $viewargs($view) "--" $viewfiles($view)] r]
} err]} {
error_popup "Error executing git rev-list: $err"
next prev parent reply other threads:[~2007-09-02 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 22:31 gitk fails to parse git log output in 1.5.3 Jing Xue
2007-09-02 23:16 ` Junio C Hamano [this message]
2007-09-03 1:25 ` Jing Xue
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=7vzm04odze.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jingxue@digizenstudio.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 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.