I dont usually read info pages since I have trouble navigating them. But reading what you quoted made clear what happened. I would personally have preferred it if seq would notice when the increment is not doing anything, and instead of producing infinite output, complained and quit as it does when the starting value is too large. The fact that it does that in one case is part of why I thought it was a bug to not do it in another. But to be honest, I'd have implemented unlimited integers rather than using floating point, perhaps by making it use Python under the covers, since that's how Python normally works. Well maybe I wouldn't do it that way in coreutils.... But I'd do it. It's not that hard if you're not doing multiply or divide. On Mon, Oct 29, 2018 at 4:00 PM C de-Avillez