aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPádraig Brady <P@draigBrady.com>2010-05-16 01:14:51 +0100
committerPádraig Brady <P@draigBrady.com>2010-05-16 01:28:32 +0100
commit9464ce21074a44b794d48bb9b93366d9d46bc7b5 (patch)
tree45e036560ee8be6046ddd9005f7811b02a8c9a84
parentsort: --debug: output data independent warnings and info (diff)
downloadcoreutils-9464ce21074a44b794d48bb9b93366d9d46bc7b5.tar.gz
coreutils-9464ce21074a44b794d48bb9b93366d9d46bc7b5.zip
doc: fix sort info about version sort skipping blanks
* doc/coreutils.text (sort invocation): leading blanks are significant for 'V'.
-rw-r--r--doc/coreutils.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index cd99bd0b7..77434e972 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -4120,7 +4120,7 @@ the start and end positions of a field specification, and if it is
inherited from the global options it will be attached to both.
If input lines can contain leading or adjacent blanks and @option{-t}
is not used, then @option{-k} is typically combined with @option{-b} or
-an option that implicitly ignores leading blanks (@samp{MghnV}) as otherwise
+an option that implicitly ignores leading blanks (@samp{Mghn}) as otherwise
the varying numbers of leading blanks in fields can cause confusing results.
If the start position in a sort field specifier falls after the end of