[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: sort -nu: bug or feature?
From: |
Stepan Kasal |
Subject: |
Re: sort -nu: bug or feature? |
Date: |
Thu, 9 Sep 2004 10:21:42 +0200 |
User-agent: |
Mutt/1.4.1i |
Hello Paul,
On Wed, Sep 08, 2004 at 12:33:17PM -0700, Paul Eggert wrote:
> I changed the documentation as follows to try to help clarify things.
thanks to Andrew for noticing this and to Paul for the doc fix.
But I think the documentation still misses one thing, see the patch below.
Stepan
2004-09-09 Stepan Kasal <address@hidden>
* coreutils.texi (sort invocation): Explain interaction of --unique
with the last-resort comparison.
--- coreutils-5.0/doc/coreutils.texi.orig 2003-04-02 20:19:11.000000000
+0200
+++ coreutils-5.0/doc/coreutils.texi 2004-09-09 10:22:07.000000000 +0200
@@ -2854,7 +2854,11 @@
Finally, as a last resort when all keys compare equal (or if no ordering
options were specified at all), @command{sort} compares the entire lines.
The last resort comparison honors the @option{--reverse} (@option{-r})
-global option. The @option{--stable} (@option{-s}) option disables this
+global option. If a field or a global option was specified, the
address@hidden (@option{-u}) option disables this last-resort
+comparison.
+
+The @option{--stable} (@option{-s}) option also disables the
last-resort comparison so that lines in which all fields compare equal
are left in their original relative order. If no fields or global
options are specified, @option{--stable} (@option{-s}) has no effect.
- Re: sort -nu: bug or feature?, (continued)
Re: sort -nu: bug or feature?, Chris F.A. Johnson, 2004/09/08
Re: sort -nu: bug or feature?, Andreas Schwab, 2004/09/09
Re: sort -nu: bug or feature?, Paul Eggert, 2004/09/08
- Re: sort -nu: bug or feature?,
Stepan Kasal <=
Re: sort -nu: bug or feature?, Stepan Kasal, 2004/09/09