* xargs/xargs.1: point out that -e and -i were removed from POSIX long
ago, in 2004, and that -p was added in the same version of the
standard.
* doc/find.texi: Likewise.
---
 doc/find.texi | 13 +++++++++++--
 xargs/xargs.1 | 27 ++++++++++++++++++---------
 2 files changed, 29 insertions(+), 11 deletions(-)

diff --git a/doc/find.texi b/doc/find.texi
index 71b80f53..b149cea8 100644
--- a/doc/find.texi
+++ b/doc/find.texi
@@ -4059,7 +4059,14 @@ string.  The @samp{-e} form of this option is deprecated 
in favour of
 the POSIX-compliant @samp{-E} option, which you should use instead.  As
 of GNU @code{xargs} version 4.2.9 (2004), the default behaviour of @code{xargs}
 is not to have a logical end-of-file marker string.  The POSIX standard
-(IEEE Std 1003.1, 2004 Edition) allows this.
+(IEEE Std 1003.1, 2004 Edition) allows this.  The @samp{-e}
+option was removed from the POSIX standard (IEEE Std 1003.1, 2004
+Edition).
+
+Other implementations of @code{xargs} may have a default logical
+end-of-file string, so if you want to portably ensure
+that no logical end-of-file string is in use, use
+@code{-E ""} to disable the logical end-of-file string.
 
 The logical end-of-file marker string is not treated specially if the
 @samp{-d} or the @samp{-0} options are in effect.  That is, when either
@@ -4079,7 +4086,9 @@ instead, the input is split at newlines only.
 If @var{replace-str} is omitted (omitting it is allowed only for @samp{-i}
 and @samp{--replace}), it defaults to @samp{@{@}} (like for @samp{find -exec}).
 Implies @samp{-x} and @samp{-L 1}.
-The @samp{-i} option is deprecated in favour of the @samp{-I} option.
+The @samp{-i} option was removed from the POSIX standard (IEEE Std
+1003.1, 2004 Edition), and so while GNU @code{xargs} continues to
+support it, it is best to use @samp{-I} instead.
 
 @item -L @var{max-lines}
 @itemx --max-lines@r{[}=@var{max-lines}@r{]}
diff --git a/xargs/xargs.1 b/xargs/xargs.1
index 9f750c43..b7111c19 100644
--- a/xargs/xargs.1
+++ b/xargs/xargs.1
@@ -148,6 +148,13 @@ If neither
 nor
 .B \-e
 is used, no end-of-file string is used.
+Other implementations of
+.B xargs
+may have a default logical end-of-file string, so if you want to
+portably ensure that no logical end-of-file string is in use, use
+.B \-E ""
+to disable the logical end-of-file string.
+See also STANDARDS CONFORMANCE.
 .
 .TP
 .\" We use font selection escape sequences here because usage of `\c` in
@@ -163,15 +170,10 @@ option.
 Use
 .B \-E
 instead,
-because it is POSIX-compliant while this option is not.
-If
-.I eof-str
-is omitted, there is no end-of-file string.
-If neither
-.B \-E
-nor
+because it is still POSIX-compliant whereas the
 .B \-e
-is used, no end-of-file string is used.
+option was removed from the POSIX standard (IEEE Std 1003.1, 2004
+Edition).
 .
 .TP
 .BI \-I\*(~~ replace-str
@@ -209,7 +211,9 @@ argument is missing, the effect is the same as
 \*(rq.
 The
 .B \-i
-option is deprecated; use
+option was removed from the POSIX standard (IEEE Std 1003.1, 2004
+Edition).
+Use
 .B \-I
 instead.
 .
@@ -562,6 +566,11 @@ The long-standing
 option of
 .B xargs
 appeared first in Issue 8 (IEEE Std 1003.1\-2024) of the POSIX standard.
+The long-standing
+.B \-p
+option of GNU
+.B xargs
+was added to Issue 6 (IEEE Std 1003.1\-2004).
 .P
 As of GNU
 .I findutils
-- 
2.47.3


Reply via email to