[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mistake in sort -k argument processing?
From: |
Andreas Schwab |
Subject: |
Re: mistake in sort -k argument processing? |
Date: |
Fri, 22 Dec 2006 19:20:15 +0100 |
User-agent: |
Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.91 (gnu/linux) |
Evan Hunt <address@hidden> writes:
> In the end spec, however, characters *still* count from 1, but there's a
> wholly unnecessary option to specify the full field by adding .0--which
> can be done equally well by *not* adding .0. It's a no-op. We just
> ignore it.
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.
Andreas.
--
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- 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 <=
- Re: mistake in sort -k argument processing?, Evan Hunt, 2006/12/22
- Re: mistake in sort -k argument processing?, Jim Meyering, 2006/12/22
- Re: mistake in sort -k argument processing?, Evan Hunt, 2006/12/27