{"thread":{"id":"32241","subject":"gitk: highlighting commits \"touching path\" with globs doesn't work for files list","startedAt":"2012-11-29T13:51:30Z","lastAt":"2012-11-29T13:51:30Z","messageCount":1,"participants":["Yaroslav Halchenko"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"204255","messageId":"20121129135130.GA24445@onerussian.com","threadId":"32241","inReplyTo":null,"subject":"gitk: highlighting commits \"touching path\" with globs doesn't work for files list","fromName":"Yaroslav Halchenko","fromEmail":"debian@onerussian.com","sentAt":"2012-11-29T13:51:30Z","receivedAt":"2012-11-29T13:51:30Z","isPatch":false,"sender":{"key":"debian@onerussian.com","avatar":"https://gravatar.com/avatar/9d2f005048a0274a9c26bc47a51f580e2bf631dfedfdb18370f65e08e4250317?d=mp&s=160"},"body":"Hi GIT Gurus,\n\nHighlighting files (in patch view) and commits which modified those\nfiles is a really nice feature to have.   Often it is needed to\nhighlight based on a glob expression for files, e.g. '*Makefile*'\n-- that seems to highlight the commits but files in the patch view\nare no longer highlighted, which significantly reduces usefulness of\nsuch a feature.\n\nAlso, those choices (Exact/IgnCase/Regexp) seems to have no relation\nwith the edit box when looking for \"touching path\" files, so shouldn't\nit be somehow disabled/emptied to avoid users trying to create the\nultimate filepattern regexp for no good reason?  (the same for next\nfield on where to search through -- All Fields/... ) ;)\n\n-- \nYaroslav O. Halchenko\nPostdoctoral Fellow,   Department of Psychological and Brain Sciences\nDartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755\nPhone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419\nWWW:   http://www.linkedin.com/in/yarik        \n"}]}