GNU bug report logs - #23110
seq apparent bug

Previous Next

Package: coreutils;

Reported by: Маренков Евгений <hotpil <at> mail.ru>

Date: Thu, 24 Mar 2016 17:23:03 UTC

Severity: normal

Tags: fixed

Done: Assaf Gordon <assafgordon <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

Message #11 received at 23110 <at> debbugs.gnu.org (full text, mbox):

From: Leslie S Satenstein <lsatenstein <at> yahoo.com>
To: Bernhard Voelker <mail <at> bernhard-voelker.de>, 
 Маренков Евгений <hotpil <at> mail.ru>, 
 "23110 <at> debbugs.gnu.org" <23110 <at> debbugs.gnu.org>
Subject: Re: bug#23110: seq apparent bug
Date: Thu, 24 Mar 2016 19:11:39 +0000 (UTC)

[Message part 1 (text/plain, inline)]
Should not an increment of zero be flagged as an error, and not ignored?
 Regards 
 Leslie
 Mr. Leslie Satenstein
Montréal Québec, Canada



      From: Bernhard Voelker <mail <at> bernhard-voelker.de>
 To: Маренков Евгений <hotpil <at> mail.ru>; 23110 <at> debbugs.gnu.org 
 Sent: Thursday, March 24, 2016 1:44 PM
 Subject: bug#23110: seq apparent bug
   
On 03/24/2016 04:28 PM, Маренков Евгений wrote:
> I have recently noticed an apparent bug in 'seq'. If one runs
> seq -w 2 1 10
> everything works fine.
> But 
> seq -w 2 0 10
> falls into endless loop ...

Thanks for the report.
However, I don't think this is a bug but more a misunderstanding
on your side how seq works.  It's clearly documented that the
second number (if 3 are given) is the increment.  As you passed
0 as value, the target 10 is never reached, and therefore seq
continues to produce output.  Thus, it exactly does what you
told it to do.  What else would you expect?

Have a nice day,
Berny





  
[Message part 2 (text/html, inline)]
This bug report was last modified 6 years and 210 days ago.

Previous Next

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