{"thread":{"id":"10265","subject":"[bug] gitk can not read history if diff color is enabled","startedAt":"2007-10-13T14:18:18Z","lastAt":"2007-10-13T14:49:51Z","messageCount":3,"participants":["Mike Sharov","Johannes Schindelin","Michele Ballabio"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"55603","messageId":"4710D3AA.8000502@softhome.net","threadId":"10265","inReplyTo":null,"subject":"[bug] gitk can not read history if diff color is enabled","fromName":"Mike Sharov","fromEmail":"msharov@softhome.net","sentAt":"2007-10-13T14:18:18Z","receivedAt":"2007-10-13T14:18:18Z","isPatch":false,"sender":{"key":"msharov@softhome.net","avatar":null},"body":"Reproduced in git version 1.5.3.4.217.gbfc1, although it's been this way\nfor a while. To see the bug, enable color diff with\n\n[diff]\ncolor\n\nand launch gitk on any repository (like the Linux kernel tree). The\nresult is a dialog box \"Can't parse git log output '\\x1b[33mcommit\" etc.\nqgit can still view the history without errors, so I guess it must be\npossible to somehow turn off color for a specific query.\n-- \nMike\nmsharov@users.sourceforge.net\n"},{"id":"55605","messageId":"Pine.LNX.4.64.0710131541330.25221@racer.site","threadId":"10265","inReplyTo":"4710D3AA.8000502@softhome.net","subject":"Re: [bug] gitk can not read history if diff color is enabled","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-10-13T14:43:07Z","receivedAt":"2007-10-13T14:43:07Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 13 Oct 2007, Mike Sharov wrote:\n\n> Reproduced in git version 1.5.3.4.217.gbfc1, although it's been this way\n> for a while. To see the bug, enable color diff with\n> \n> [diff]\n> color\n> \n> and launch gitk on any repository (like the Linux kernel tree).\n\nThanks for the bug report.\n\nThis is fixed in http://hjemli.net/git/git/log/?h=q/mb/gitk/log--no-color\n(which will be applied without any doubt once our king penguin comes \nback).\n\nCiao,\nDscho\n"},{"id":"55606","messageId":"200710131649.51496.barra_cuda@katamail.com","threadId":"10265","inReplyTo":"4710D3AA.8000502@softhome.net","subject":"Re: [bug] gitk can not read history if diff color is enabled","fromName":"Michele Ballabio","fromEmail":"barra_cuda@katamail.com","sentAt":"2007-10-13T14:49:51Z","receivedAt":"2007-10-13T14:49:51Z","isPatch":false,"sender":{"key":"barra_cuda@katamail.com","avatar":"https://avatars.githubusercontent.com/u/16371673?v=4"},"body":"On Saturday 13 October 2007, Mike Sharov wrote:\n> Reproduced in git version 1.5.3.4.217.gbfc1, although it's been this way\n> for a while. To see the bug, enable color diff with\n> \n> [diff]\n> color\n> \n> and launch gitk on any repository (like the Linux kernel tree). The\n> result is a dialog box \"Can't parse git log output '\\x1b[33mcommit\" etc.\n> qgit can still view the history without errors, so I guess it must be\n> possible to somehow turn off color for a specific query.\n\nA patch was posted, and is queued here:\n\n\thttp://hjemli.net/git/git/commit/?h=q/mb/gitk/log--no-color\n"}]}