And now that I'm cleaning the patches applied to the debian package,
here is another tiny patch.
Cheers,
Santiago
>From 1c86cafdc67c157ce8744da0b32151d1e0f77545 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Santiago=20Ruano=20Rinc=C3=B3n?= <santi...@debian.org>
Date: Fri, 4 Mar 2016 20:01:48 +0100
Subject: [PATCH] doc: consistent PCRE doc between grep.1.in and grep.texi
---
doc/grep.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/grep.texi b/doc/grep.texi
index 8883b27..39d6276 100644
--- a/doc/grep.texi
+++ b/doc/grep.texi
@@ -1102,7 +1102,7 @@ expressions), separated by newlines, any of which is to be matched.
@opindex -P
@opindex --perl-regexp
@cindex matching Perl regular expressions
-Interpret the pattern as a Perl regular expression.
+Interpret the pattern as a Perl regular expression (PCRE).
This is highly experimental and
@samp{grep@ -P} may warn of unimplemented features.
@@ -1127,7 +1127,7 @@ Regular expressions are constructed analogously to arithmetic expressions,
by using various operators to combine smaller expressions.
@command{grep} understands
three different versions of regular expression syntax:
-``basic,'' (BRE) ``extended'' (ERE) and ``perl''.
+``basic,'' (BRE) ``extended'' (ERE) and ``perl'' (PCRE).
In GNU @command{grep},
there is no difference in available functionality between the basic and
extended syntaxes.
--
2.4.6
