[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#19287: Request to improve the Man document for "sort."
From: |
Leslie Satenstein |
Subject: |
bug#19287: Request to improve the Man document for "sort." |
Date: |
Sat, 06 Dec 2014 08:02:32 -0500 |
I had a lot of head scratching until someone clarified the
documentation.
Here is the line and explanation that bothers me.
Explanation of -k ...
-k, --key=POS1[,POS2]
start a key at POS1 (origin 1), end it at POS2 (default end
of line)
with accompanying explanation
POS is F[.C][OPTS], where F is the field number and C the
character position in the field; both are origin 1. If neither
-t nor -b is in effect, characters in a field are counted from
the beginning of the preceding whitespace. OPTS is one or more
single-letter ordering options, which override global ordering
options for that key. If no key is given, use the entire line as
the key.
It was not clear to me that when -t was used with a field delimited
file, then to sort only by the entire enclosed field, we need to specify
-k F.F and that -k F'.F' may occur multiple times.
It was only with the SEE ALSO that with the visit to info coreutils sort
invocation that explanation about sorting fields was described.
Can a clarification of the explanation for -k be provided.
I would add one sentence after the last line of the above indented
paragraph.
For additional rules pertaining to the sort of field delimited
records, consult info coreutils sort invocation
We should not have to visit two references (man and info) in order to
setup sort keys.
Regards
Leslie Satenstein
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#19287: Request to improve the Man document for "sort.",
Leslie Satenstein <=