From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14022 invoked from network); 4 Jun 1997 14:46:04 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 4 Jun 1997 14:46:04 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id KAA15934; Wed, 4 Jun 1997 10:37:58 -0400 (EDT) Resent-Date: Wed, 4 Jun 1997 10:37:58 -0400 (EDT) To: zsh-workers@math.gatech.edu Path: mason From: mason@primenet.com.au (Geoff Wing) Newsgroups: lists.zsh.workers Subject: Re: bug?!? Date: 4 Jun 1997 14:41:40 GMT Organization: PrimeNet Message-ID: References: <199706041351.PAA00824@warande0147.warande.ruu.nl> Reply-To: mason@primenet.com.au NNTP-Posting-Host: coral.primenet.com.au X-Newsreader: slrn (0.9.3.2 UNIX) Resent-Message-ID: <"6vwzv1.0.vu3.5tNbp"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/3193 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu On 4 Jun 1997 23:57:11 +1000, Xander van Wiggen wrote: :First of all: THANKS FOR ZSH! :However, I've encountered the following: :2. In zsh 3.0.2, NOBADPATTERN does not seem to work, at least not in : interactive mode. I do not know if this is a 'feature' or something obvious : that I overlooked, but if I do "mdir a:*.txt" with BAD_PATTERN switched OFF, : zsh tells me that it can't find a match in the current directory. : This is not a problem caused by mdir, it happens with echo too: : % setopt nobadpattern : % echo foo* : zsh: no matches found: foo* : In bash this example simply prints "foo*" on the screen. Neither of those were bad patterns. Perhaps you want: NO_NOMATCH A bad pattern is something like % echo [100- -- Geoff Wing [mason@primenet.com.au] Technical Manager Phone : +61-3-9818 2977 PrimeNet - Internet Consultancy Facsimile: +61-3-9819 3788 Web : Mobile : 0412 162 441