Documentation Suggestions for FSEARCH Documentation

[Jay Sage]

I think that it is not clear that without the /V option, not only does the command display only the first match, it doesn't even look for all the matches. If one wants the variable _fsearch_matches to have the number of total matches, the /V option is required. It might be better if the help for /V said something like the following:

/V Find and display all matching text (FSEARCH defaults to only finding and displaying the first match in each file)

TCC(34.00.12): C:\temp>fsearch /t"line" junk.txt & echo Variable _fsearch_matches = %_fsearch_matches

---- C:\temp\junk.txt
Line 9

Matching lines: 1        Matching files: 1        Total files searched: 1
Variable _fsearch_matches = 1

If one wants the count of total matches but does not want to see them all, one can add the /U option or redirect the output to nul.

TCC(34.00.12): C:\temp>fsearch /t"line" /v junk.txt >nul & echo Variable _fsearch_matches = %_fsearch_matches
Variable _fsearch_matches = 9

TCC(34.00.12): C:\temp>fsearch /t"line" /u /v junk.txt & echo Variable _fsearch_matches = %_fsearch_matches

Matching lines: 9        Matching files: 1        Total files searched: 1
Variable _fsearch_matches = 9

 

[Alpengreis]

@Jay Sage

Yes, I agree, that should be pointed out in the help (not within the /V help text only).

 

[rconn]

This behavior is identical to (the elderly) FFIND.

 

[Jay Sage]

Fine. The same documentation improvement should be made for the FFIND command as well.