git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* gitk fails to parse git log output in 1.5.3
@ 2007-09-02 22:31 Jing Xue
  2007-09-02 23:16 ` Junio C Hamano
  0 siblings, 1 reply; 3+ messages in thread
From: Jing Xue @ 2007-09-02 22:31 UTC (permalink / raw)
  To: git

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?

Thanks.
-- 
Jing Xue

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: gitk fails to parse git log output in 1.5.3
  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
  2007-09-03  1:25   ` Jing Xue
  0 siblings, 1 reply; 3+ messages in thread
From: Junio C Hamano @ 2007-09-02 23:16 UTC (permalink / raw)
  To: Jing Xue; +Cc: git

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"

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: gitk fails to parse git log output in 1.5.3
  2007-09-02 23:16 ` Junio C Hamano
@ 2007-09-03  1:25   ` Jing Xue
  0 siblings, 0 replies; 3+ messages in thread
From: Jing Xue @ 2007-09-03  1:25 UTC (permalink / raw)
  To: Junio C Hamano; +Cc: git


On Sun, Sep 02, 2007 at 04:16:05PM -0700, Junio C Hamano wrote:
> 
> This will quickly turn into an FAQ.

Indeed. I went and added it to the Wiki/FAQ.

Also I noticed that git-log was missing the descriptions for '--color'
and '--no-color'.


Signed-off-by: Jing Xue <jingxue@digizenstudio.com>
---
 Documentation/git-log.txt |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 5ec547c..c42ca89 100644
--- a/Documentation/git-log.txt
+++ b/Documentation/git-log.txt
@@ -72,6 +72,14 @@ include::pretty-options.txt[]
 	Note that only message is considered, if also a diff is shown
 	its size is not included.
 
+--color::
+	Show colored log entries. Same as if `color.diff` were set to
+    "true".
+
+--no-color::
+	Turn off colored log entries, even when `color.diff` sets the
+    default to color output.
+
 <paths>...::
 	Show only commits that affect the specified paths.
 
-- 
1.5.3

^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-09-03  1:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2007-09-03  1:25   ` Jing Xue

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).