/[pcre]/code/trunk/doc/pcregrep.1

Diff of /code/trunk/doc/pcregrep.1

Parent Directory | Revision Log | View Patch Patch

-revision 148 by ph10,
Mon Apr 16 13:25:10 2007 UTC
+revision 279 by ph10,
Tue Dec  4 20:01:43 2007 UTC
 Line 23 
 without delimiters. For example:
  .sp
  If you attempt to use delimiters (for example, by surrounding a pattern with
  slashes, as is common in Perl scripts), they are interpreted as part of the
- pattern. Quotes can of course be used on the command line because they are
+ pattern. Quotes can of course be used to delimit patterns on the command line
- interpreted by the shell, and indeed they are required if a pattern contains
+ because they are interpreted by the shell, and indeed they are required if a
- white space or shell metacharacters.
+ pattern contains white space or shell metacharacters.
  .P
  The first argument that follows any option settings is treated as the single
  pattern to be matched when neither \fB-e\fP nor \fB-f\fP is present.
 Line 41 
 For example:
  .sp
  By default, each line that matches the pattern is copied to the standard
  output, and if there is more than one file, the file name is output at the
- start of each line. However, there are options that can change how
+ start of each line, followed by a colon. However, there are options that can
- \fBpcregrep\fP behaves. In particular, the \fB-M\fP option makes it possible to
+ change how \fBpcregrep\fP behaves. In particular, the \fB-M\fP option makes it
- search for patterns that span line boundaries. What defines a line boundary is
+ possible to search for patterns that span line boundaries. What defines a line
- controlled by the \fB-N\fP (\fB--newline\fP) option.
+ boundary is controlled by the \fB-N\fP (\fB--newline\fP) option.
  .P
  Patterns are limited to 8K or BUFSIZ characters, whichever is the greater.
  BUFSIZ is defined in \fB<stdio.h>\fP.
 Line 116 
 option), or "skip" (silently skip the pa
  are read as if they were ordinary files. In some operating systems the effect
  of reading a directory like this is an immediate end-of-file.
  .TP
- \fB-e\fP \fIpattern\fP, \fB--regex=\fP\fIpattern\fP,
+ \fB-e\fP \fIpattern\fP, \fB--regex=\fP\fIpattern\fP, \fB--regexp=\fP\fIpattern\fP
- \fB--regexp=\fP\fIpattern\fP Specify a pattern to be matched. This option can
+ Specify a pattern to be matched. This option can be used multiple times in
- be used multiple times in order to specify several patterns. It can also be
+ order to specify several patterns. It can also be used as a way of specifying a
- used as a way of specifying a single pattern that starts with a hyphen. When
+ single pattern that starts with a hyphen. When \fB-e\fP is used, no argument
- \fB-e\fP is used, no argument pattern is taken from the command line; all
+ pattern is taken from the command line; all arguments are treated as file
- arguments are treated as file names. There is an overall maximum of 100
+ names. There is an overall maximum of 100 patterns. They are applied to each
- patterns. They are applied to each line in the order in which they are defined
+ line in the order in which they are defined until one matches (or fails to
- until one matches (or fails to match if \fB-v\fP is used). If \fB-f\fP is used
+ match if \fB-v\fP is used). If \fB-f\fP is used with \fB-e\fP, the command line
- with \fB-e\fP, the command line patterns are matched first, followed by the
+ patterns are matched first, followed by the patterns from the file, independent
- patterns from the file, independent of the order in which these options are
+ of the order in which these options are specified. Note that multiple use of
- specified. Note that multiple use of \fB-e\fP is not the same as a single
+ \fB-e\fP is not the same as a single pattern with alternatives. For example,
- pattern with alternatives. For example, X|Y finds the first character in a line
+ X|Y finds the first character in a line that is X or Y, whereas if the two
- that is X or Y, whereas if the two patterns are given separately,
+ patterns are given separately, \fBpcregrep\fP finds X if it is present, even if
- \fBpcregrep\fP finds X if it is present, even if it follows Y in the line. It
+ it follows Y in the line. It finds Y only if there is no X in the line. This
- finds Y only if there is no X in the line. This really matters only if you are
+ really matters only if you are using \fB-o\fP to show the part(s) of the line
- using \fB-o\fP to show the portion of the line that matched.
+ that matched.
  .TP
  \fB--exclude\fP=\fIpattern\fP
  When \fBpcregrep\fP is searching the files in a directory as a consequence of
 Line 220 
 the previous 8K characters (or all the p
  are guaranteed to be available for lookbehind assertions.
  .TP
  \fB-N\fP \fInewline-type\fP, \fB--newline=\fP\fInewline-type\fP
- The PCRE library supports four different conventions for indicating
+ The PCRE library supports five different conventions for indicating
  the ends of lines. They are the single-character sequences CR (carriage return)
- and LF (linefeed), the two-character sequence CRLF, and an "any" convention, in
+ and LF (linefeed), the two-character sequence CRLF, an "anycrlf" convention,
+ which recognizes any of the preceding three types, and an "any" convention, in
  which any Unicode line ending sequence is assumed to end a line. The Unicode
  sequences are the three just mentioned, plus VT (vertical tab, U+000B), FF
  (formfeed, U+000C), NEL (next line, U+0085), LS (line separator, U+2028), and
- PS (paragraph separator, U+0029).
+ PS (paragraph separator, U+2029).
  .sp
  When the PCRE library is built, a default line-ending sequence is specified.
  This is normally the standard sequence for the operating system. Unless
  otherwise specified by this option, \fBpcregrep\fP uses the library's default.
- The possible values for this option are CR, LF, CRLF, or ANY. This makes it
+ The possible values for this option are CR, LF, CRLF, ANYCRLF, or ANY. This
- possible to use \fBpcregrep\fP on files that have come from other environments
+ makes it possible to use \fBpcregrep\fP on files that have come from other
- without having to modify their line endings. If the data that is being scanned
+ environments without having to modify their line endings. If the data that is
- does not agree with the convention set by this option, \fBpcregrep\fP may
+ being scanned does not agree with the convention set by this option,
- behave in strange ways.
+ \fBpcregrep\fP may behave in strange ways.
  .TP
  \fB-n\fP, \fB--line-number\fP
  Precede each output line by its line number in the file, followed by a colon
-Line 245 
 the filename is also being output, it pr
+Line 246 
 the filename is also being output, it pr
  \fB-o\fP, \fB--only-matching\fP
  Show only the part of the line that matched a pattern. In this mode, no
  context is shown. That is, the \fB-A\fP, \fB-B\fP, and \fB-C\fP options are
- ignored.
+ ignored. If there is more than one match in a line, each of them is shown
+ separately. If \fB-o\fP is combined with \fB-v\fP (invert the sense of the
+ match to find non-matching lines), no output is generated, but the return code
+ is set appropriately.
  .TP
  \fB-q\fP, \fB--quiet\fP
  Work quietly, that is, display nothing except error messages. The exit
-Line 387 
 Cambridge CB2 3QH, England.
+Line 391 
 Cambridge CB2 3QH, England.
  .rs
  .sp
  .nf
- Last updated: 06 March 2007
+ Last updated: 04 December 2007
  Copyright (c) 1997-2007 University of Cambridge.
  .fi

 Legend:



Removed from v.148
 


changed lines


 
Added in v.279
 Legend:



Removed from v.148
 


changed lines


 
Added in v.279
-Removed from v.148
+Added in v.279

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12