Johannes Sixt <j.sixt@xxxxxxxxxxxxx> writes: > Mark Blakeney schrieb: >> This seems to me to be a straight out bug but given I've had no response here >> and given this is such a simple issue then I guess it's not a bug and I'm just >> missing something? Please somebody, why does gitk (usually) not show the subset >> list of files affected when you give it a path? >> >> E.g. If I am in a src dir then "gitk ." does not list files. Neither does "gitk >> $PWD" nor "gitk ../src". However "cd ..; git src" does list files!? > > gitk doesn't list the files in your examples because the patterns you gave > are not initial substrings of any files in the list. Yes, but if you are in src/ and run "gitk .", then... - clicking on a commit runs "diff-tree $commit .", that lists src/hello.c, src/goodbye.c, etc. - gitk tries to filter paths read from diff-tree with the "." given from the command line as the filter---it removes paths that do not match. So the only case that would produce any output would be for you to have: src/src/hello.c src/frotz.c and run cd src && gitk src whose invocation of "diff-tree src" will show _only_ src/src/hello.c and then the filter procedure will limit it to whatever begins with src/ (which would be everything). That does not sound very useful to me... -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html