AlDanial

`--include-content=` will only count files whose contents match the regex. If nothing else, combined with `--by-file`, cloc will identify such files but won't count the number of instances where the...

@tfadler : give the 1.96.1 Windows executable at https://github.com/AlDanial/cloc/releases a try. It includes PR #686 by @RyanMcC that uses `Win32::LongPath` to resolve long paths on Windows.

Two thoughts came to mind: try running cloc at the parent directory of your deep structure 1) from WSL or 2) using the "Git for Bash" terminal that comes with...

``.csproj`` and ``.fsproj`` are already recognized: » cloc --show-ext csproj csproj -> MSBuild script » cloc --show-ext fsproj fsproj -> XML Difficult to say which association is most applicable: dotnet,...

Well, I did take my time :) I reran the original case reported as showing 3 lines instead of 4. cloc 1.98 reports the answer is 4 although I don't...

The reason cloc counts the `#!` line is because this *is* a line of code. The invoked interpreter acts on arguments given to it. Here's an example: #!/usr/bin/perl -n -i...

But it isn't just `perl` that uses `#!` arguments. My work colleagues frequently add `-u` to the `python` `#!` line to un-buffer stdout and stderr, ie, `#!/usr/bin/env python3 -u`. In...

None of the ``--match-*`` or ``--not-match-*`` switches may be repeated. I didn't see the need since a single regex can handle multiple cases. Your two ``--not-match-f`` cases can be condensed...

It's not a big ask and I'm familiar with additive options (cloc's ``--force-lang`` and ``--script-lang`` can be specified multiple times). Still, the request will need to get on the back...

I've begun work on this; try the latest commit to kick the tires on additive ``--not-match-f`` and ``--not-match-d``