Subject: Re: RFC seq(1) command
To: None <tech-userlevel@NetBSD.org>
From: Ignatios Souvatzis <is@netbsd.org>
List: tech-userlevel
Date: 01/12/2005 16:08:16
--Bu8it7iiRSEf40bY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 12, 2005 at 09:05:18AM -0500, Perry E. Metzger wrote:
>=20
> Brian Ginsbach <ginsbach@NetBSD.org> writes:
> > Hmm, in some ways jot does too much!  The command line syntax is
> > different.  I think for this reason alone it is probably easier to
> > have a different command.  Now, I suppose that seq could be a shell
> > script wrapper around jot.  Some additional functionality would
> > need to be added to jot; the equal width option.  Still this would
> > be even less bug for bug compatible with other existing implementations
> > of seq.  I wrote the current C version before I knew about jot.
> >
> > There are 3rd party tools/scripts that expect seq not jot.
>=20
> What OSes include seq at the moment?

What do SUSV and POSIX say?

	-is

--Bu8it7iiRSEf40bY
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFB5T1fN4tiz3B8hB0RAmfkAJ9YkfrIeD7BZAnpy4igIwvI/U060gCg5F/U
9cTsQXimZlZJQTcs2QDrFqo=
=JTgM
-----END PGP SIGNATURE-----

--Bu8it7iiRSEf40bY--