On 2018-08-27 04:53 PM, Jeff King wrote:
> On Mon, Aug 27, 2018 at 04:23:34PM -0700, Stas Bekman wrote:
[...]
>> How can I get GIT_TRACE's run_command to show the arguments passed to
>> the filter? I looked at various other debug environment variables in
>> git's manual, but I don't see anything that would enable that level of
>> debug.
[...]
> You can work around it with some shell hackery:
>
> git config filter.foo.clean 'f() { echo >&2 "cleaning $1"; myfilter ...; }; f %f'
>
> and then even without GIT_TRACE, you get:
>
> $ git add .
> cleaning .gitattributes
>
> Or if you really just want to trigger for GIT_TRACE, try just this:
>
> $ git config filter.foo.clean 'f() { myfilter; }; f %f'
> 19:52:52.874064 [pid=14719] git.c:415 trace: built-in: git add .
> 19:52:52.875115 [pid=14719] run-command.c:637 trace: run_command: 'f() { myfilter; }; f '\''.gitattributes'\'''
Your suggestions do the trick, Jeff. Thank you.
1. To benefit others who might be looking for something similar may I
post your suggestions as an answer to:
<https://stackoverflow.com/questions/51995773/getting-git-to-show-specific-filenames-it-is-running-content-filters-on>?
2. Is there no way to get git to do the filename reporting as a normal
GIT_TRACE behavior? I don't know anything about its internal workings,
but it surely must knows which file it operates on when it opens it and
sends its data as stdin to the content filter. It makes the debugging so
much easier when one can see what files are being worked on. So perhaps
this utility can be made available to all not just as a hack/workaround.
--
________________________________________________
Stas Bekman <'))))>< <'))))><
https://stasosphere.com https://chestofbooks.com
https://experientialsexlab.com https://stason.org
https://stasosphere.com/experience-life/my-books
