https://gunkies.org/index.php?action=history&feed=atom&title=32v_1m_grep 2026-05-12T04:00:21Z Revision history for this page on the wiki MediaWiki 1.30.1 https://gunkies.org/w/index.php?title=32v_1m_grep&diff=6970&oldid=prev 2009-10-26T14:15:09Z

<p>New page: GREP(1) UNIX Programmer&#039;s Manual GREP(1) == NAME == grep, egrep, fgrep - search a file for a pattern == SYNOPSIS == grep [ option ] ... expression [...</p> <p><b>New page</b></p><div>GREP(1) UNIX Programmer's Manual GREP(1)<br /> <br /> <br /> <br /> == NAME ==<br /> grep, egrep, fgrep - search a file for a pattern<br /> <br /> == SYNOPSIS ==<br /> grep [ option ] ... expression [ file ] ...<br /> <br /> egrep [ option ] ... [ expression ] [ file ] ...<br /> <br /> fgrep [ option ] ... [ strings ] [ file ]<br /> <br /> == DESCRIPTION ==<br /> Commands of the _g_r_e_p family search the input _f_i_l_e_s (standard<br /> input default) for lines matching a pattern. Normally, each<br /> line found is copied to the standard output. _G_r_e_p patterns<br /> are limited regular expressions in the style of _e_d(1); it<br /> uses a compact nondeterministic algorithm. _E_g_r_e_p patterns<br /> are full regular expressions; it uses a fast deterministic<br /> algorithm that sometimes needs exponential space. _F_g_r_e_p<br /> patterns are fixed strings; it is fast and compact. The<br /> following options are recognized.<br /> <br /> -v All lines but those matching are printed.<br /> <br /> -x (Exact) only lines matched in their entirety are<br /> printed (_f_g_r_e_p only).<br /> <br /> -c Only a count of matching lines is printed.<br /> <br /> -l The names of files with matching lines are listed<br /> (once) separated by newlines.<br /> <br /> -n Each line is preceded by its relative line number in<br /> the file.<br /> <br /> -b Each line is preceded by the block number on which it<br /> was found. This is sometimes useful in locating disk<br /> block numbers by context.<br /> <br /> -e _e_x_p_r_e_s_s_i_o_n<br /> Same as a simple _e_x_p_r_e_s_s_i_o_n argument, but useful when<br /> the _e_x_p_r_e_s_s_i_o_n begins with a -.<br /> <br /> -f _f_i_l_e<br /> The regular expression (_e_g_r_e_p) or string list (_f_g_r_e_p)<br /> is taken from the _f_i_l_e.<br /> <br /> In all cases the file name is shown if there is more than<br /> one input file. Care should be taken when using the charac-<br /> ters $ * [ ^ | ( ) and \ in the _e_x_p_r_e_s_s_i_o_n as they are also<br /> meaningful to the Shell. It is safest to enclose the entire<br /> _e_x_p_r_e_s_s_i_o_n argument in single quotes ' '.<br /> <br /> _F_g_r_e_p searches for lines that contain one of the (newline-<br /> separated) _s_t_r_i_n_g_s.<br /> <br /> _E_g_r_e_p accepts extended regular expressions. In the follow-<br /> ing description `character' excludes newline:<br /> <br /> A \ followed by a single character other than newline<br /> matches that character.<br /> <br /> The character ^ ($) matches the beginning (end) of a<br /> line.<br /> <br /> A . matches any character.<br /> <br /> A single character not otherwise endowed with special<br /> meaning matches that character.<br /> <br /> A string enclosed in brackets [] matches any single<br /> character from the string. Ranges of ASCII character<br /> codes may be abbreviated as in `a-z0-9'. A ] may occur<br /> only as the first character of the string. A literal -<br /> must be placed where it can't be mistaken as a range<br /> indicator.<br /> <br /> A regular expression followed by * (+, ?) matches a<br /> sequence of 0 or more (1 or more, 0 or 1) matches of<br /> the regular expression.<br /> <br /> Two regular expressions concatenated match a match of<br /> the first followed by a match of the second.<br /> <br /> Two regular expressions separated by | or newline match<br /> either a match for the first or a match for the second.<br /> <br /> A regular expression enclosed in parentheses matches a<br /> match for the regular expression.<br /> <br /> The order of precedence of operators at the same parenthesis<br /> level is [] then *+? then concatenation then | and newline.<br /> <br /> == SEE ALSO ==<br /> [[32v 1m ed|ed(1)]], [[32v 1m sed|sed(1)]], [[32v 1m sh|sh(1)]]<br /> <br /> == DIAGNOSTICS ==<br /> Exit status is 0 if any matches are found, 1 if none, 2 for<br /> syntax errors or inaccessible files.<br /> <br /> == BUGS ==<br /> Ideally there should be only one _g_r_e_p, but we don't know a<br /> single algorithm that spans a wide enough range of space-<br /> time tradeoffs.<br /> <br /> Lines are limited to 256 characters; longer lines are trun-<br /> cated.<br /> <br /> [[Category:32v man section 1]]</div>

Neozeed