Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: CSH_NULL_GLOB broken?
- X-seq: zsh-users 887
- From: <hzoli@xxxxxxxxxxxx> (Zoltan T. Hidvegi)
- To: stephen.talley@xxxxxxxxxxxxxxx (Steve Talley)
- Subject: Re: CSH_NULL_GLOB broken?
- Date: Mon, 9 Jun 1997 19:39:17 -0400 (EDT)
- Cc: zsh-users@xxxxxxxxxxxxxxx
- In-reply-to: <199706092049.OAA05185@xxxxxxxxxxxxxxxxxxxxxx> from Steve Talley at "Jun 9, 97 02:49:10 pm"
Steve Talley wrote:
> CSH_NULL_GLOB doesn't appear to work in 3.1.0:
>
> % unsetopt nomatch
> % unsetopt nullglob
> % setopt cshnullglob
> % ls -d /tmp
> /tmp/
> % ls -d /blah*
> zsh: no match
> % ls -d /tmp /blah*
> zsh: no match
>
> The last command, according to the zshoptions man page, should have
> listed /tmp and ignored the fact that nothing matches /blah*. Am I
> missing something?
That's the documented behaviour, and that's how csh works (tcsh at least).
The manual says: `do not report an error unless all the patterns in a
command have no matches'. The above command has only one pattern, /blah*
and it has no matches, so the error comes. /tmp is not a pattern since it
does not conain any glob special characters.
Zoltan
Messages sorted by:
Reverse Date,
Date,
Thread,
Author