批处理之find详解（Batch find detail）.docVIP

批处理之find详解（Batch find detail） When Im looking for a string, the first command I think of is not the find Im talking about in this article, but the more powerful command findstr. Im so dependent on findstr that when I explain the find command to you, Ill have to punch the find / command in the CMD window, and then press the return key heavily. Find /? The execution results soon got a full information, help out, compared with the findstr command more than 10 switches, find has only 5 switches, is pale into insignificance by comparison. The basic format of the find command is this: find, the string to be searched for, the file to be searched here, the string to be searched for, this content is essential, and the quotation marks are also required. For example, find bathome d:\test.txt, which represents the text file in the D packing directory, test.txt searches for all rows containing the string bathome. The results for find will come in two cases: 1, when the file contains the search string, the string will return to the location of the whole line, the specific format: the first line is - X (* * * said the search for the file name, without the quotes), second lines began to appear on the whole line containing the character content; 2, when no search string appears in a document, the result of find simply returns - * * * this line (* * * said the search for the file name, without the quotes). When looking for a specified string, there are occasions where you need to distinguish case from case, and on some occasions you dont care about the case. How do you implement these requirements? Very simple, at the time of find, add or remove /i switch is the specific usage: find /i Abc test.txt said insens, the text contains Abc, ABC, ABC, are considered; find Abc test.txt is strictly distinguish the character size to write, but not only, Abc. ABC, ABC, such as character. Sometimes, we need not to find a string, but to determine which line does not contain specific string, this t