- Dec
- 238
- 2
TCC 20.00.14 x64 Windows 10 [Version 6.3.14393]
TCC Build 14 Windows 10 Build 14393
Here's the @everything[] example shown in the v.20 online help:
On my system, the above returns three or four "hits." Then this command:
... returns only a single "hit" — the very first one shown when parameter "1" is not used.
Different kind of results with wildcards, though.
... returns around 85 "hits" to the console. But an attempt to get only one match by using the optional numeric parameter fails:
... returns "Echo is OFF".
Shouldn't this last example return the first "hit" that's displayed when the parameter "1" has not been used?
This, however, does work — note that there's an additional character in the file spec:
It returns the fully-qualified name of a single file on this system matching "*b8*.tmp".
Why did it fail for "*8*.tmp" when both "f" and "1" params were used?
TCC Build 14 Windows 10 Build 14393
Here's the @everything[] example shown in the v.20 online help:
echo %@everything[tcc.exe,f]
On my system, the above returns three or four "hits." Then this command:
echo %@everything[tcc.exe,f,1]
... returns only a single "hit" — the very first one shown when parameter "1" is not used.
Different kind of results with wildcards, though.
echo %@everything[*8*.tmp,f]
... returns around 85 "hits" to the console. But an attempt to get only one match by using the optional numeric parameter fails:
echo %@everything[*8*.tmp,f,1]
... returns "Echo is OFF".
Shouldn't this last example return the first "hit" that's displayed when the parameter "1" has not been used?
This, however, does work — note that there's an additional character in the file spec:
%@everything[*b8*.tmp,f,1]
It returns the fully-qualified name of a single file on this system matching "*b8*.tmp".
Why did it fail for "*8*.tmp" when both "f" and "1" params were used?