--uZ3hkaAS1mZxFaxD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Christos Zoulas <christos@zoulas.com> wrote:
> In article <20040417170638.GB13247@netmeister.org>,
> Jan Schaumann <jschauma@netmeister.org> wrote:

> >Secondly, if n is 0, csh treats it as a director name.  Even though
> >'pushd +0' is a no-op, I believe it should not try to interpret '+0' as
> >a directory.  Especially, since directories named '+n' (for n !=3D 0) ne=
ed
> >to be escaped if they are to be used as names rather than number.  (Ie
> >to push the directory named '+1' on the stack, you'd have to do 'pushd
> >\+1' - the same should hold for '+0')
> >
> >Am I correct with this?
>=20
> Yes, but historically this is how csh has behaved. I.e. +0 was interpreted
> as a directory. I don't think it matters.

Question is, do we want to retain this behaviour for historic reasons or
rather do the (albeit not really helpful) right thing, then?

-Jan

--=20
DON'T PANIC!

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

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

iD8DBQFAg8UFfFtkr68iakwRAhI2AKCYwPmWQk3LuEeh0sjASaGbTPkeWACfaYAe
S9TTrIwyxsrnJrDgjtapKNQ=
=yfmi
-----END PGP SIGNATURE-----

--uZ3hkaAS1mZxFaxD--