Windows shell utilities are another victory for Cygwin

C:\Symbian\UIQ3.1SDK\epoc32>find --help
FIND: Parameter format not correct

C:\Symbian\UIQ3.1SDK\epoc32>find -h
FIND: Parameter format not correct

C:\Symbian\UIQ3.1SDK\epoc32>find /h
FIND: Invalid switch

C:\Symbian\UIQ3.1SDK\epoc32>find
FIND: Parameter format not correct

C:\Symbian\UIQ3.1SDK\epoc32>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.

C:\Symbian\UIQ3.1SDK\epoc32>grep
'grep' is not recognized as an internal or external command,
operable program or batch file.

And that’s why I’m installing Cygwin on my computer now…

3 thoughts on “Windows shell utilities are another victory for Cygwin

  1. If you need “grep”, you should have used “findstr”. It covers pretty much all of grep’s functionalities.

    As you know I was porting scripts from shell -> Windows and the first versions where all BATs ;-)

    Ok, the scripts aren’t that advanced, but they do all the standard stuff, and I couldn’t find anything in the shells that couldn’t be done in the Windows shell in a similar approach.

    But hey, I like cygwin anyway :-)

  2. grep in Windows is “start” > “find files and directories”… that’s what a MSCE once said to me.

Comments are closed.