summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPádraig Brady <P@draigBrady.com>2020-11-18 14:00:43 +0000
committerPádraig Brady <P@draigBrady.com>2020-11-18 14:00:43 +0000
commitc3a5280731ee096cb156d87eaa38c1d887490380 (patch)
treef521b6cbbf575d3a7d032896ebe88d9753ecc2b0
parent2bc66c5ea7e507786a45c1b6b15fe74a338240f4 (diff)
doc: mention that sort -g supports hex numbers
* doc/coreutils.texi (sort invocation): Mention explicitly that --general-numeric-sort supports arbitrary format hex numbers, but also mention that consistent case/width hex numbers can be sorted faster with a standard sort.
-rw-r--r--doc/coreutils.texi6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 99f6d9fb8..5ac3745bd 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -4397,6 +4397,12 @@ Use this option only if there is no alternative; it is much slower than
@option{--numeric-sort} (@option{-n}) and it can lose information when
converting to floating point.
+You can use this option to sort hexadecimal numbers prefixed with
+@samp{0x} or @samp{0X}, where those numbers are not fixed width,
+or of varying case. However for hex numbers of consistent case,
+and left padded with @samp{0} to a consistent width, a standard
+lexicographic sort will be faster.
+
@item -h
@itemx --human-numeric-sort
@itemx --sort=human-numeric