Re: newbie question: simulating wildcards with piping
From: Barry Margolin (barmar_at_alum.mit.edu)
Date: 01/30/05
- Next message: snowcrash27_at_hotmail.com: "Re: while [...] && [...] this doesn't work"
- Previous message: drcode_at_gmail.com: "Re: newbie question: simulating wildcards with piping"
- In reply to: drcode_at_gmail.com: "Re: newbie question: simulating wildcards with piping"
- Next in thread: Keith Thompson: "Re: newbie question: simulating wildcards with piping"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 29 Jan 2005 20:29:11 -0500
In article <1107046934.720467.135820@c13g2000cwb.googlegroups.com>,
drcode@gmail.com wrote:
> > What didn't work?
>
> Well, I'm running the bash command shell and my command is a compiled
> unix command ("sid2wav" in this case). Typing:
>
> sid2wav *.sid
>
> or
>
> sid2wav *
>
> does not work for me, but
>
> find . -name *.sid -exec sid2wav {} \;
That shouldn't work if there are any .sid files in the current
directory. Find searches recursively, wildcards only expand to files in
the directory specified in the wildcard path (the current directory by
default).
-- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me ***
- Next message: snowcrash27_at_hotmail.com: "Re: while [...] && [...] this doesn't work"
- Previous message: drcode_at_gmail.com: "Re: newbie question: simulating wildcards with piping"
- In reply to: drcode_at_gmail.com: "Re: newbie question: simulating wildcards with piping"
- Next in thread: Keith Thompson: "Re: newbie question: simulating wildcards with piping"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]