Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: is text file?
- X-seq: zsh-workers 3537
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx (Zsh hackers list)
- Subject: Re: is text file?
- Date: Mon, 29 Sep 1997 08:26:52 -0700
- In-reply-to: <199709291025.MAA06202@xxxxxxxxxx>
- References: <199709291025.MAA06202@xxxxxxxxxx>
On Sep 29, 12:25pm, Peter Stephenson wrote:
} Subject: Re: is text file?
}
} "Bart Schaefer" wrote:
} > % ls **/*~*(${~${(j/|/)fignore}})(.)
} >
} > (Somebody tell me why the extra ${~...} is needed in that expression.)
}
} The `|' needs to be tokenised. Otherwise, it looks for the pattern
} '.o|~|.pro|.dvi' or whatever as a literal file name.
That was the answer I wanted, thanks.
} Or do you mean, why can't I put the ~ in the same ${...}
I would have asked that in a separate message to zsh-workers, but I figured
out
} % echo *(${(j/|/)~fignore})
shortly after I'd sent the previous message.
} (Or did you mean, why doesn't it go between the { and the (, in which
} case the answer is `it just doesn't, but maybe it should say so in
} the manual'.)
In spite of Zoltan's response to this, I don't think it would hurt for the
manual to make an explicit statements about mixing ${( with ${~ ${= etc.,
particularly because of things like ${(j//)#foo} -ne ${#{$(j//)foo}}.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author