From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu (Zsh hackers list)
Subject: Re: is text file?
Date: Mon, 29 Sep 1997 08:26:52 -0700 [thread overview]
Message-ID: <970929082652.ZM11122@candle.brasslantern.com> (raw)
In-Reply-To: <199709291025.MAA06202@sgi.ifh.de>
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
prev parent reply other threads:[~1997-09-29 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <970928170607.ZM7789@candle.brasslantern.com>
1997-09-29 10:25 ` Peter Stephenson
1997-09-29 12:37 ` Zoltan T. Hidvegi
1997-09-29 15:26 ` Bart Schaefer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=970929082652.ZM11122@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).