Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: path and += troubles
- X-seq: zsh-workers 22041
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: path and += troubles
- Date: Sun, 27 Nov 2005 18:40:48 +0000
- In-reply-to: <200511271334.jARDYWrO004473@xxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <200511271334.jARDYWrO004473@xxxxxxxxxxxxxxxxx>
On Nov 27, 1:34pm, Peter Stephenson wrote:
} Subject: Re: path and += troubles
}
} > schaefer<508> echo $1+=($2)
} > zsh: no match
} > schaefer<509> $1+=($2)
} > schaefer<510>
} >
} > Where's my "no match" error in the second case?
}
} I'm having a hard time coming up with a combination of options and
} arguments that does this.
Starting from "zsh -f":
zagzig% setopt cshnullglob
zagzig% echo $1+=($2)
zsh: no match
zagzig% $1+=($2)
zagzig%
The problem of course is that cshnullglob is supposed to be like nomatch
if *nothing* matches -- it's only supposed to be like nullglob if at
least one of several patterns matches.
} But didn't you say the problem was with NULLGLOB?
I originally [in the -users thread] mentioned that the error message
vanishes with either nullglob or cshnullglob. After I figured out that
it happens because the test string I was using was somehow a valid glob
qualifier -- that is, "(2)" is a valid qualifier, though I have no idea
what meaning it can possibly have -- then I said [on -workers] that it
was limited to cshnullglob.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author