In Windows, what are the differences between the find and findstr commands?
Both seem to search for text in files:
find
C:\> find /?
Searches for a text string in a file or files.
FIND [/V] [/C] [/N] [/I] [/OFF[LINE]] "string" [[drive:][path]filename[ ...]] /V Displays all lines NOT containing the specified string. /C Displays only the count of lines containing the string. /N Displays line numbers with the displayed lines. /I Ignores the case of characters when searching for the string. /OFF[LINE] Do not skip files with offline attribute set. "string" Specifies the text string to find. [drive:][path]filename Specifies a file or files to search.
If a path is not specified, FIND searches the text typed at the prompt
or piped from another command.findstr
C:\> findstr /?
Searches for strings in files.
FINDSTR [/B] [/E] [/L] [/R] [/S] [/I] [/X] [/V] [/N] [/M] [/O] [/P] [/F:file] [/C:string] [/G:file] [/D:dir list] [/A:color attributes] [/OFF[LINE]] strings [[drive:][path]filename[ ...]] /B Matches pattern if at the beginning of a line. /E Matches pattern if at the end of a line. /L Uses search strings literally. /R Uses search strings as regular expressions. /S Searches for matching files in the current directory and all subdirectories. /I Specifies that the search is not to be case-sensitive. /X Prints lines that match exactly. /V Prints only lines that do not contain a match. /N Prints the line number before each line that matches. /M Prints only the filename if a file contains a match. /O Prints character offset before each matching line. /P Skip files with non-printable characters. /OFF[LINE] Do not skip files with offline attribute set. /A:attr Specifies color attribute with two hex digits. See "color /?" /F:file Reads file list from the specified file(/ stands for console). /C:string Uses specified string as a literal search string. /G:file Gets search strings from the specified file(/ stands for console). /D:dir Search a semicolon delimited list of directories strings Text to be searched for. [drive:][path]filename Specifies a file or files to search.
Use spaces to separate multiple search strings unless the argument is prefixed
with /C. For example, 'FINDSTR "hello there" x.y' searches for "hello" or
"there" in file x.y. 'FINDSTR /C:"hello there" x.y' searches for
"hello there" in file x.y.
Regular expression quick reference: . Wildcard: any character * Repeat: zero or more occurences of previous character or class ^ Line position: beginning of line $ Line position: end of line [class] Character class: any one character in set [^class] Inverse class: any one character not in set [x-y] Range: any characters within the specified range \x Escape: literal use of metacharacter x \<xyz Word position: beginning of word xyz\> Word position: end of word
For full information on FINDSTR regular expressions refer to the online Command
Reference.6 Answers
As shown above, findstr adds regular expressions support, so it's more like grep.
The Old New Thing blog touches on these tools in this post.
In summary: tools developed in parallel to suit slightly different needs; they were simply never combined into one single tool.
1Findstr has more search options and supports regular expressions. I found that findstr does not work with wild cards in the file name.
The command below returns all occurences of search string in multiple files with the pattern Quant_2013-10-25_*.log
find /I "nFCT255c9A" D:\Comp1\Logs\Quant_2013-10-25_*.log The following command returns nothing or simply does not work
findstr nFCT255c9A D:\Comp1\Logs\Quantum_2013-10-25_*.logBesides those mentioned:
2
findstr extends the functionality of find with several useful features. Some of the key additions include
- findstr supports multiple search strings
- findstr can take as input a file containing file names or directories to search
- findstr supports regular expression
Neither function is suitable for large files or large numbers of files.
1Another difference (that often trips me up):
FIND weirdly requires the search pattern to be in quotation marks. FINDSTR does not.
> FIND needle haystack.txt
FIND: Parameter format not correct
> FIND "needle" haystack.txt
---------- HAYSTACK.TXT
needleThis is particularly odd, since the two main command line parsers used on Windows will drop the quotes when they split the command line into an array of arguments. Therefore FIND is grabbing the command line directly from the OS and doing its own parsing.
Like most other programs, FINDSTR is flexible about the quotation marks. You don't have to use them unless you need to include white space in the pattern.
> FINDSTR needle haystack.txt
needle
> FINDSTR "needle" haystack.txt
needle
