[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mistake in sort -k argument processing?
From: |
Jim Meyering |
Subject: |
Re: mistake in sort -k argument processing? |
Date: |
Fri, 22 Dec 2006 21:06:07 +0100 |
Evan Hunt <address@hidden> wrote:
>> Just like you can ignore a .1 in the start spec. But you can't ignore a
>> .0 in a start spec, because it is wrong. You can't denote the _end_ of
>> the start field.
>
> Very well. In that case, let's edit the documentation to reflect that .0
> represents the end of the field, and I'll be happy.
I would welcome a patch (to coreutils.texi) to do that.
- mistake in sort -k argument processing?, Evan Hunt, 2006/12/22
- Re: mistake in sort -k argument processing?, Andreas Schwab, 2006/12/22
- Re: mistake in sort -k argument processing?, Evan Hunt, 2006/12/22
- Re: mistake in sort -k argument processing?, Andreas Schwab, 2006/12/22
- Re: mistake in sort -k argument processing?, Evan Hunt, 2006/12/22
- Re: mistake in sort -k argument processing?, Andreas Schwab, 2006/12/22
- Re: mistake in sort -k argument processing?, Evan Hunt, 2006/12/22
- Re: mistake in sort -k argument processing?,
Jim Meyering <=
- Re: mistake in sort -k argument processing?, Evan Hunt, 2006/12/27