[Emacs-bug-tracker] bug#8070: closed (cut command)

[GNU bug Tracking System]

Your message dated Thu, 17 Feb 2011 23:44:52 +0100
with message-id <address@hidden>
and subject line Re: bug#8070: cut command
has caused the GNU bug report #8070,
regarding cut command
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
8070: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8070
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: cut command Date: Thu, 17 Feb 2011 16:19:53 -0600

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
address@hidden
ph:856.848.9005 Ext 220

The Wyanoke Group
http://www.wyanokegroup.com

 

 

 

--- End Message ---

> --- Begin Message ---
>
>
>
> 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-"
>
>
> --- End Message ---