{"thread":{"id":"16331","subject":"gitk touching paths highlighting oddity","startedAt":"2008-11-14T17:51:59Z","lastAt":"2008-11-14T17:51:59Z","messageCount":1,"participants":["Mark Burton"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"95805","messageId":"loom.20081114T173548-920@post.gmane.org","threadId":"16331","inReplyTo":null,"subject":"gitk touching paths highlighting oddity","fromName":"Mark Burton","fromEmail":"markb@ordern.com","sentAt":"2008-11-14T17:51:59Z","receivedAt":"2008-11-14T17:51:59Z","isPatch":false,"sender":{"key":"markb@ordern.com","avatar":null},"body":"\nHi,\n\nUsing gitk (1.6.0.4) within a given subdirectory of a working tree, I wanted to\nsee those commits that affected files in the current directory so I selected\ntouching paths\" and then typed \".\" into the entry field (That's right isn't it?)\n\nOn pressing the Next button, not only was a relevant commit successfully found\nand highlighted (commit message boldened) but all of the \".\" characters in the\ncommit message list were given a yellow background (as if I was \nsearching the text for \".\"). Surely the yellow text highlighting shouldn't\nhappen when finding paths?\n\nA quick look at the gitk code left me no wiser hence this email.\n\nMark\n"}]}