If you use spaces, you need the /C: option to pass the the literal string(s) to the regex /R option. Once the it gets to the regex, it’s treated as a regex. That said, this is typical MS trash. Use two regex search strings The bottom line is that you have to use 2 strings … Read more
This works for me: findstr /r “^[1-9][0-9]*$ ^-[1-9][0-9]*$ ^0$” If you don’t use the /c option, the <Strings> argument is treated as a space-separated list of search strings, which makes the space a sort of crude replacement for the | construct. (As long as your regexes don’t contain spaces, that is.)
You could use a look-ahead assertion: (?!999)\d{3} This example matches three digits other than 999. But if you happen not to have a regular expression implementation with this feature (see Comparison of Regular Expression Flavors), you probably have to build a regular expression with the basic features on your own. A compatible regular expression with … Read more
Preface Much of the information in this answer has been gathered based on experiments run on a Vista machine. Unless explicitly stated otherwise, I have not confirmed whether the information applies to other Windows versions. FINDSTR output The documentation never bothers to explain the output of FINDSTR. It alludes to the fact that matching lines … Read more