summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2006-06-28 23:50:21 +0000
committerPaul Eggert <eggert@cs.ucla.edu>2006-06-28 23:50:21 +0000
commit5b3614ac912a9d7f66029e4ef54857deb55e715b (patch)
treec93bb78bdfb88ca12b8f2193f724a90c67f899a5
parent3869e2919673f91152f351a0e5211ddaec74682c (diff)
downloadcoreutils-5b3614ac912a9d7f66029e4ef54857deb55e715b.tar.xz
(sort invocation): 'sort +1 -2' is now supported
even when conforming to POSIX 1003.1-2001, since this is a pure extension to POSIX.
-rw-r--r--doc/coreutils.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index d8cc5b6a2..0b142c7ad 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -3681,11 +3681,13 @@ numbers of leading blanks in fields can cause confusing results.
Keys can span multiple fields.
@vindex _POSIX2_VERSION
+@vindex POSIXLY_CORRECT
On older systems, @command{sort} supports an obsolete origin-zero
syntax @samp{+@var{pos1} [-@var{pos2}]} for specifying sort keys.
This obsolete behavior can be enabled or disabled with the
@env{_POSIX2_VERSION} environment variable (@pxref{Standards
-conformance}).
+conformance}); it can also be enabled when @env{POSIXLY_CORRECT} is
+not set by using the obsolete syntax with @samp{-@var{pos2}} present.
Scripts intended for use on standard hosts should avoid obsolete
syntax and should use @option{-k} instead. For example, avoid