GNU bug report logs - #8070
cut command

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: George Gallen <ggallen <at> wyanokegroup.com>
Subject: bug#8070: closed (Re: bug#8070: cut command)
Date: Thu, 17 Feb 2011 22:36:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#8070: cut command

which was filed against the coreutils package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 8070 <at> debbugs.gnu.org.

-- 
8070: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8070
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Jim Meyering <jim <at> meyering.net>
To: George Gallen <ggallen <at> wyanokegroup.com>
Cc: 8070-done <at> debbugs.gnu.org
Subject: Re: bug#8070: cut command
Date: Thu, 17 Feb 2011 23:44:52 +0100

George Gallen wrote:
> I'm not sure whether this is a bug or not.
>
> On Redhat Enterprise Linux, the cut command will accept the following " cut -c0-5 " (Cut ver 5.97)
> On Fedora it will not accept the 0, it must be " cut -c1-5 " (cut ver 8.5)
>
> Although both are functionally the same, they seem to only return 5 characters
> The script it was written in worked without problems from Redhat 7.2 to present RHEL
> I only noticed the problem with fedora 13 and 14.
>
> I was able to copy the cut command from RHEL to Fedora 14 and it works fine. What am losing
>   between these two versions?
>
> Was there a divergence somewhere along the way where cut stopped tolerating the
>    the 0 base index?

Right.  That change was due to a bug fix.
Here's part of coreutils' NEWS file:

* Noteworthy changes in release 6.9.91 (2007-12-15) [beta]

  cut now diagnoses a range starting with zero (e.g., -f 0-2) as invalid;
  before, it would treat it as if it started with 1 (-f 1-2).

  "cut -f 2-0" now fails; before, it was equivalent to "cut -f 2-"

[Message part 3 (message/rfc822, inline)]

From: George Gallen <ggallen <at> wyanokegroup.com>
To: "bug-coreutils <at> gnu.org" <bug-coreutils <at> gnu.org>
Subject: cut command
Date: Thu, 17 Feb 2011 16:19:53 -0600

[Message part 4 (text/plain, inline)]

I'm not sure whether this is a bug or not.

On Redhat Enterprise Linux, the cut command will accept the following " cut -c0-5 " (Cut ver 5.97)
On Fedora it will not accept the 0, it must be " cut -c1-5 " (cut ver 8.5)

Although both are functionally the same, they seem to only return 5 characters
The script it was written in worked without problems from Redhat 7.2 to present RHEL
I only noticed the problem with fedora 13 and 14.

I was able to copy the cut command from RHEL to Fedora 14 and it works fine. What am losing
  between these two versions?

Was there a divergence somewhere along the way where cut stopped tolerating the
   the 0 base index?

Thanks


George Gallen
Senior Programmer/Analyst
Accounting/Data Division, EDI Administrator
ggallen <at> wyanokegroup.com
ph:856.848.9005 Ext 220
The Wyanoke Group
http://www.wyanokegroup.com

[Message part 5 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.