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