{"thread":{"id":"37384","subject":"Anyone know the innards of the gitk program?","startedAt":"2014-08-20T08:51:56Z","lastAt":"2014-08-20T08:51:56Z","messageCount":1,"participants":["John M. Dlugosz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"248008","messageId":"20938-1408524736-805990@sneakemail.com","threadId":"37384","inReplyTo":null,"subject":"Anyone know the innards of the gitk program?","fromName":"John M. Dlugosz","fromEmail":"ngnr63q02@sneakemail.com","sentAt":"2014-08-20T08:51:56Z","receivedAt":"2014-08-20T08:51:56Z","isPatch":false,"sender":{"key":"ngnr63q02@sneakemail.com","avatar":null},"body":"I knew that gitk is written in a scripting language, so I had high hopes of making a \nlittle tweak to it.  But, alas, it's 12000 lines of languages I don't know!\n\nThe farthest I got was finding “text $cflist \\” on line 2381 and the corroborating comment \n“# lower right” just above it.\n\nWhat I want to accomplish is to highlight specific words in the Patch view; in particular \ncertain path element names to indicate files I'm specifically interested in reviewing and \nthose that I'm specifically not at all interested in.\n\nConsidering the way it works — Tk widgets — that ought to be easy.  I've used Perl/Tk in \nthe past and can look up the parameters to different element types.  But I have no idea \nwhere to put such a change, or the general flow of the program in general.\n\nIs anyone knowledgeable in the inner workings of this program willing to help me out?\n\nI've tried a few git repository GUI programs (on Windows) and always end up gravitating \nback to Git Gui and gitk !\n\n—John\n"}]}