Date: Mon, 13 May 1996 15:46:41 +0000 (GMT) From: Gabor Zahemszky <zgabor@CoDe.hu> To: dan@dan.emsphone.com (Dan Nelson) Cc: freebsd-questions@freebsd.org Subject: Re: Please Help ... I am locked out of a FreeBSD machine Message-ID: <199605131546.PAA00315@CoDe.CoDe.hu> In-Reply-To: <199605091609.LAA25050@dan.emsphone.com> from "Dan Nelson" at May 9, 96 11:09:34 am
next in thread | previous in thread | raw e-mail | index | archive | help
> I've been wondering what you all were talking about, since on my machine, > "echo .*" does NOT list "." or "..". I checked the man pages for zsh, and > sure enough, under "FILENAME GENERATION (GLOBBING)", I see: > > No filename generation pattern matches the files "." or "..". > > Can ash maybe be patched to do this also? I can't think of a case where you > would EVER want to match '.' or '..' in a wildcard. > > -Dan Nelson > dan@dan.emsphone.com > The problem is that the original shells generates . and .., and so many people like compatibility. I don't know zsh, but AT&T's ksh, and bash, the original UCB csh and tcsh all of them generate . and .. - the one I know, is the pdksh which doesn't do it. If a shell doesn't generate it, isn't compatible with the wrong (?) Unix standard. Sorry. -- Gabor Zahemszky <zgabor@CoDe.hu> -:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:-:- Earth is the cradle of human sense, but you can't stay in the cradle forever. Tsiolkovsky
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605131546.PAA00315>