SGrep Issue with Wildcard (-wc) Switch

[mek]

I'm using the version of sgrep distributed with VS 2023 and am encountering an issue when using the -wc switch to include multiple file name masks for searching against.  It would appear that when this option is enabled, the searching behaves in a manner that would be consistent with the -w (Match whole word) being enabled as well -- this is not what I desire

failing example:  sgrep -i -t -pc jojo -wc dbo.Test* dbo.RunTest*

Text that looks like "test_jojo" will not be matched, but if the command is changed to use individual sgrep invocations for each wildcard mask, the match will be found...

passing example:  sgrep -i -t -pc jojo dbo.Test*

Don't know when this behavior started as this is really the first time I've attempted to use the -wc switch...

Thanks for your help.

[Clark]

If you're on Linux or macOS, you should quote the wildcards to make sure something weird doesn't happen.

sgrep -i -t -pc jojo -wc "dbo.Test*" "dbo.RunTest*"

[mek]

Thanks Clark -- unfortunately quoting or not quoting the wildcard parameters does not make a difference in the results (this is on Windows btw). 

If I were a betting man, it really does look like there is a command line argument parsing issue with sgrep where it's accidentally turning on the "-w" switch when only a -wc switch is being supplied (again that's just my conclusion based on the observed behavior).

[Clark]

Interesting. It doesn't seem to work right unless you specify a path like this:

    sgrep -i -t -pc jojo . -wc dbo.Test* dbo.RunTest*

the above is equivalent to this:

    sgrep -i -t -pc jojo dbo.Test* dbo.RunTest*

The reason -wc was added is for users to avoid having to repeat long paths multiple times.

consider the following:

     sgrep -i -t -pc jojo c:\some\really\long\long\path\dbo.Test* c:\some\really\long\long\path\dbo.RunTest*

In this case use -wc like this:

     sgrep -i -t -pc jojo c:\some\really\long\long\path -wc dbo.Test* dbo.RunTest*

For now, always specify a path when using -wc.

We will look into this. It should still work without a path.

[mek]

Thanks Clark

I concur that your "fix" of explicitly providing a "default" directory (i.e. .) when using -wc does indeed produce the results I would expect.