# [bug] gitk can not read history if diff color is enabled

3 messages from 2007-10-13 to 2007-10-13. Participants: Mike Sharov, Johannes Schindelin, Michele Ballabio.
Thread: https://gitlist.dev/t/10265

## Mike Sharov, 2007-10-13 14:18

Subject: [bug] gitk can not read history if diff color is enabled
Message-ID: <4710D3AA.8000502@softhome.net>
URL: https://gitlist.dev/e/4710D3AA.8000502%40softhome.net

```
Reproduced in git version 1.5.3.4.217.gbfc1, although it's been this way
for a while. To see the bug, enable color diff with

[diff]
color

and launch gitk on any repository (like the Linux kernel tree). The
result is a dialog box "Can't parse git log output '\x1b[33mcommit" etc.
qgit can still view the history without errors, so I guess it must be
possible to somehow turn off color for a specific query.
-- 
Mike
msharov@users.sourceforge.net

```

## Johannes Schindelin, 2007-10-13 14:43

Subject: Re: [bug] gitk can not read history if diff color is enabled
Message-ID: <Pine.LNX.4.64.0710131541330.25221@racer.site>
URL: https://gitlist.dev/e/Pine.LNX.4.64.0710131541330.25221%40racer.site
In-Reply-To: <4710D3AA.8000502@softhome.net>

```
Hi,

On Sat, 13 Oct 2007, Mike Sharov wrote:

> Reproduced in git version 1.5.3.4.217.gbfc1, although it's been this way
> for a while. To see the bug, enable color diff with
> 
> [diff]
> color
> 
> and launch gitk on any repository (like the Linux kernel tree).

Thanks for the bug report.

This is fixed in http://hjemli.net/git/git/log/?h=q/mb/gitk/log--no-color
(which will be applied without any doubt once our king penguin comes 
back).

Ciao,
Dscho

```

## Michele Ballabio, 2007-10-13 14:49

Subject: Re: [bug] gitk can not read history if diff color is enabled
Message-ID: <200710131649.51496.barra_cuda@katamail.com>
URL: https://gitlist.dev/e/200710131649.51496.barra_cuda%40katamail.com
In-Reply-To: <4710D3AA.8000502@softhome.net>

```
On Saturday 13 October 2007, Mike Sharov wrote:
> Reproduced in git version 1.5.3.4.217.gbfc1, although it's been this way
> for a while. To see the bug, enable color diff with
> 
> [diff]
> color
> 
> and launch gitk on any repository (like the Linux kernel tree). The
> result is a dialog box "Can't parse git log output '\x1b[33mcommit" etc.
> qgit can still view the history without errors, so I guess it must be
> possible to somehow turn off color for a specific query.

A patch was posted, and is queued here:

	http://hjemli.net/git/git/commit/?h=q/mb/gitk/log--no-color

```