Return to cpgrep.hlp CVS log

Up to [OS/2 SDKs] / os2sdk / demos / apps / cpgrep

Annotation of os2sdk/demos/apps/cpgrep/cpgrep.hlp, revision 1.1.1.2

1.1       root        1: CPGREP.EXE
1.1.1.2 ! root        2: Created by Microsoft Corp. 1986
1.1       root        3: 
                      4: This program is compatible with Xenix fgrep.  It supports a subset
                      5: of the fgrep options and has a couple of extensions.  It is tailored
1.1.1.2 ! root        6: to the 286 (though it will run on an 8086) and OS/2.  It is a family
1.1       root        7: API application, so it will run in both real and protected modes.
                      8: When running in protected mode, it uses three threads in order to
                      9: do asynchronous I/O.  It is pretty fast.
                     10: 
                     11: cpgrep -? produces the following usage message:
                     12: 
                     13: usage: CPGREP [-?BElnvxy][-e][-f <file>][-i <file>][<strings>][<files>]
                     14: -? - print this message
                     15: -B - match pattern if at beginning of line
                     16: -E - match pattern if at end of line
                     17: -l - print only file name if file contains match
                     18: -n - print line number before each matching line
                     19: -v - print only lines not containing a match
                     20: -x - print lines that match exactly (-BE)
                     21: -y - treat upper and lower case as equivalent
                     22: -e - treat next argument as the search string
                     23: -f - read search strings from file named by next argument
                     24: -i - read file list from file named by next argument
                     25: 
                     26: Extensions are -B, -E, and -i.  Multiple search strings can be
                     27: specified on the command line, though the rules for doing so
                     28: vary slightly from those of Xenix fgrep because of differences
                     29: between sh and command.com.  With cpgrep.exe, any white space
                     30: character acts as a separator in the strings argument on the
                     31: command line; on Xenix with fgrep, only a newline will work.
                     32: If one wishes to search for a pattern containing white space,
                     33: use the -e switch.  When search strings are being read from
                     34: a file, however, newline is the only separator, just as it is
                     35: with fgrep on Xenix.
                     36:                                        Pete Stewart

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.