Home » Mailing list archives » git » 2007 » October » 13

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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: Mike Sharov <msharov@...>
To: <git@...>
Subject: [bug] gitk can not read history if diff color is enabled
Date: Saturday, October 13, 2007 - 10:18 am

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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
[bug] gitk can not read history if diff color is enabled, Mike Sharov, (Sat Oct 13, 10:18 am)
Re: [bug] gitk can not read history if diff color is enabled, Michele Ballabio, (Sat Oct 13, 10:49 am)
Re: [bug] gitk can not read history if diff color is enabled, Johannes Schindelin, (Sat Oct 13, 10:43 am)