The following options modify the way
cfpeek processes the
parse tree and search keys.
Use literal matching, instead of pattern matching. See literal.
Before further processing, sort parse tree lexicographically in ascending order.
Output at most number matches for each key.
Set parser type for the input file. The argument is one of: ‘grecs’, ‘path’, ‘meta1’, ‘bind’, ‘dhcpd’, and ‘git’ (case-insensitive). See Formats, for a description of each type.
Reduce the parse tree, so that each keyword occurs no more than once at each tree level.
Set a keyword path to value. The produced parse tree node will be processed as usual.
This document was generated on January 7, 2021 using makeinfo.Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.