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

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

Parent Directory | Revision Log | View Patch Patch

-revision 99 by ph10,
Tue Mar  6 12:27:42 2007 UTC
+revision 150 by ph10,
Tue Apr 17 08:22:40 2007 UTC
 Line 245 
 OPTIONS
                   lookbehind assertions.
         -N newline-type, --newline=newline-type
-                  The  PCRE  library  supports  four  different conventions for
+                  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  which
+                  character sequence CRLF, an "anycrlf" convention, which  rec-
-                  any  Unicode  line  ending sequence is assumed to end a line.
+                  ognizes  any  of the preceding three types, and an "any" con-
-                  The Unicode sequences are the three just mentioned,  plus  VT
+                  vention, in which any Unicode line ending sequence is assumed
-                  (vertical  tab,  U+000B),  FF  (formfeed,  U+000C), NEL (next
+                  to  end a line. The Unicode sequences are the three just men-
-                  line, U+0085), LS (line separator, U+2028), and PS (paragraph
+                  tioned,  plus  VT  (vertical  tab,  U+000B),  FF   (formfeed,
-                  separator, U+0029).
+                  U+000C),   NEL  (next  line,  U+0085),  LS  (line  separator,
+                  U+2028), and PS (paragraph separator, U+2029).
                   When  the  PCRE  library  is  built,  a  default  line-ending
-                  sequence  is  specified.   This  is  normally  the   standard
+                  sequence   is  specified.   This  is  normally  the  standard
                   sequence for the operating system. Unless otherwise specified
-                  by this option, pcregrep uses  the  library's  default.   The
+                  by  this  option,  pcregrep  uses the library's default.  The
-                  possible  values  for  this  option are CR, LF, CRLF, or ANY.
+                  possible values for this option are CR, LF, CRLF, ANYCRLF, or
-                  This makes it possible to use pcregrep  on  files  that  have
+                  ANY.  This  makes  it  possible to use pcregrep on files that
-                  come  from  other environments without having to modify their
+                  have come from other environments without  having  to  modify
-                  line endings. If the data that  is  being  scanned  does  not
+                  their  line  endings.  If the data that is being scanned does
-                  agree  with  the  convention set by this option, pcregrep may
+                  not agree with the convention set by  this  option,  pcregrep
-                  behave in strange ways.
+                  may behave in strange ways.
         -n, --line-number
                   Precede each output line by its line number in the file, fol-
-                  lowed  by  a colon and a space for matching lines or a hyphen
+                  lowed by a colon and a space for matching lines or  a  hyphen
-                  and a space for context lines. If the filename is also  being
+                  and  a space for context lines. If the filename is also being
                   output, it precedes the line number.
         -o, --only-matching
-                  Show  only  the  part  of the line that matched a pattern. In
+                  Show only the part of the line that  matched  a  pattern.  In
-                  this mode, no context is shown. That is, the -A, -B,  and  -C
+                  this  mode,  no context is shown. That is, the -A, -B, and -C
                   options are ignored.
         -q, --quiet
                   Work quietly, that is, display nothing except error messages.
-                  The exit status indicates whether or  not  any  matches  were
+                  The  exit  status  indicates  whether or not any matches were
                   found.
         -r, --recursive
-                  If  any given path is a directory, recursively scan the files
+                  If any given path is a directory, recursively scan the  files
-                  it contains, taking note of any --include and --exclude  set-
+                  it  contains, taking note of any --include and --exclude set-
-                  tings.  By  default, a directory is read as a normal file; in
+                  tings. By default, a directory is read as a normal  file;  in
-                  some operating systems this gives an  immediate  end-of-file.
+                  some  operating  systems this gives an immediate end-of-file.
-                  This  option  is  a  shorthand  for  setting the -d option to
+                  This option is a shorthand  for  setting  the  -d  option  to
                   "recurse".
         -s, --no-messages
-                  Suppress error  messages  about  non-existent  or  unreadable
+                  Suppress  error  messages  about  non-existent  or unreadable
-                  files.  Such  files  are quietly skipped. However, the return
+                  files. Such files are quietly skipped.  However,  the  return
                   code is still 2, even if matches were found in other files.
         -u, --utf-8
-                  Operate in UTF-8 mode. This option is available only if  PCRE
+                  Operate  in UTF-8 mode. This option is available only if PCRE
-                  has  been compiled with UTF-8 support. Both patterns and sub-
+                  has been compiled with UTF-8 support. Both patterns and  sub-
                   ject lines must be valid strings of UTF-8 characters.
         -V, --version
-                  Write the version numbers of pcregrep and  the  PCRE  library
+                  Write  the  version  numbers of pcregrep and the PCRE library
                   that is being used to the standard error stream.
         -v, --invert-match
-                  Invert  the  sense  of  the match, so that lines which do not
+                  Invert the sense of the match, so that  lines  which  do  not
                   match any of the patterns are the ones that are found.
         -w, --word-regex, --word-regexp
-Line 313 
 OPTIONS
+Line 314 
 OPTIONS
                   lent to having \b at the start and end of the pattern.
         -x, --line-regex, --line-regexp
-                  Force  the  patterns to be anchored (each must start matching
+                  Force the patterns to be anchored (each must  start  matching
-                  at the beginning of a line) and in addition, require them  to
+                  at  the beginning of a line) and in addition, require them to
-                  match  entire  lines.  This  is  equivalent to having ^ and $
+                  match entire lines. This is equivalent  to  having  ^  and  $
                   characters at the start and end of each alternative branch in
                   every pattern.
  ENVIRONMENT VARIABLES
-        The  environment  variables  LC_ALL  and LC_CTYPE are examined, in that
+        The environment variables LC_ALL and LC_CTYPE  are  examined,  in  that
-        order, for a locale. The first one that is set is  used.  This  can  be
+        order,  for  a  locale.  The first one that is set is used. This can be
-        overridden  by  the  --locale  option.  If  no  locale is set, the PCRE
+        overridden by the --locale option.  If  no  locale  is  set,  the  PCRE
         library's default (usually the "C" locale) is used.
  NEWLINES
-        The -N (--newline) option allows pcregrep to scan files with  different
+        The  -N (--newline) option allows pcregrep to scan files with different
-        newline  conventions  from  the  default.  However, the setting of this
+        newline conventions from the default.  However,  the  setting  of  this
-        option does not affect the way in which pcregrep writes information  to
+        option  does not affect the way in which pcregrep writes information to
-        the  standard  error  and  output streams. It uses the string "\n" in C
+        the standard error and output streams. It uses the  string  "\n"  in  C
-        printf() calls to indicate newlines, relying on the C  I/O  library  to
+        printf()  calls  to  indicate newlines, relying on the C I/O library to
-        convert  this  to  an  appropriate  sequence if the output is sent to a
+        convert this to an appropriate sequence if the  output  is  sent  to  a
         file.
  OPTIONS COMPATIBILITY
         The majority of short and long forms of pcregrep's options are the same
-        as  in  the  GNU grep program. Any long option of the form --xxx-regexp
+        as in the GNU grep program. Any long option of  the  form  --xxx-regexp
-        (GNU terminology) is also available as --xxx-regex (PCRE  terminology).
+        (GNU  terminology) is also available as --xxx-regex (PCRE terminology).
-        However,  the  --locale,  -M,  --multiline, -u, and --utf-8 options are
+        However, the --locale, -M, --multiline, -u,  and  --utf-8  options  are
         specific to pcregrep.
  OPTIONS WITH DATA
         There are four different ways in which an option with data can be spec-
-        ified.   If  a  short  form option is used, the data may follow immedi-
+        ified.  If a short form option is used, the  data  may  follow  immedi-
         ately, or in the next command line item. For example:
           -f/some/file
           -f /some/file
-        If a long form option is used, the data may appear in the same  command
+        If  a long form option is used, the data may appear in the same command
         line item, separated by an equals character, or (with one exception) it
         may appear in the next command line item. For example:
           --file=/some/file
           --file /some/file
-        Note, however, that if you want to supply a file name beginning with  ~
+        Note,  however, that if you want to supply a file name beginning with ~
-        as  data  in  a  shell  command,  and have the shell expand ~ to a home
+        as data in a shell command, and have the  shell  expand  ~  to  a  home
         directory, you must separate the file name from the option, because the
-        shell  does not treat ~ specially unless it is at the start of an item.
+        shell does not treat ~ specially unless it is at the start of an  item.
-        The exception to the above is the --colour  (or  --color)  option,  for
+        The  exception  to  the  above is the --colour (or --color) option, for
-        which  the  data is optional. If this option does have data, it must be
+        which the data is optional. If this option does have data, it  must  be
-        given in the first form, using an equals character. Otherwise  it  will
+        given  in  the first form, using an equals character. Otherwise it will
         be assumed that it has no data.
  MATCHING ERRORS
-        It  is  possible  to supply a regular expression that takes a very long
+        It is possible to supply a regular expression that takes  a  very  long
-        time to fail to match certain lines.  Such  patterns  normally  involve
+        time  to  fail  to  match certain lines. Such patterns normally involve
-        nested  indefinite repeats, for example: (a+)*\d when matched against a
+        nested indefinite repeats, for example: (a+)*\d when matched against  a
-        line of a's with no final digit.  The  PCRE  matching  function  has  a
+        line  of  a's  with  no  final  digit. The PCRE matching function has a
-        resource  limit that causes it to abort in these circumstances. If this
+        resource limit that causes it to abort in these circumstances. If  this
         happens, pcregrep outputs an error message and the line that caused the
-        problem  to  the  standard error stream. If there are more than 20 such
+        problem to the standard error stream. If there are more  than  20  such
         errors, pcregrep gives up.
  DIAGNOSTICS
         Exit status is 0 if any matches were found, 1 if no matches were found,
-        and  2 for syntax errors and non-existent or inacessible files (even if
+        and 2 for syntax errors and non-existent or inacessible files (even  if
-        matches were found in other files) or too many matching  errors.  Using
+        matches  were  found in other files) or too many matching errors. Using
-        the  -s  option to suppress error messages about inaccessble files does
+        the -s option to suppress error messages about inaccessble  files  does
         not affect the return code.
-Line 410 
 AUTHOR
+Line 411 
 AUTHOR
  REVISION
-        Last updated: 06 March 2007
+        Last updated: 16 April 2007
         Copyright (c) 1997-2007 University of Cambridge.

 Legend:



Removed from v.99
 


changed lines


 
Added in v.150
 Legend:



Removed from v.99
 


changed lines


 
Added in v.150
-Removed from v.99
+Added in v.150

webmaster@exim.org	ViewVC Help
Powered by ViewVC 1.1.12