Re: Problem with the find command
From: Alan Connor (xxxxxx_at_xxxx.xxx)
Date: 07/29/03
- Next message: SK: "Re: How to subscribe to this news group?"
- Previous message: Lew Pitcher: "Re: Difference in mangling"
- In reply to: Lekeas GK: "Problem with the find command"
- Next in thread: Barry Margolin: "Re: Problem with the find command"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 29 Jul 2003 17:29:53 GMT
On Tue, 29 Jul 2003 17:28:38 +0100, Lekeas GK <cj571@soi.city.ac.uk> wrote:
>
>
> Hi All,
>
> I was trying to find all css files under my directory and I noticed that
> the following commands worked fine:
>
> find . -name '*.css' -print 2>/dev/null
> find ~foo/* -name '*.css' -print 2>/dev/null
>
surprised that that one worked.
> but the following ones didn't:
>
> find ~foo -name '*.css' -print 2>/dev/null
I would think that one would.
> find /homes/foo -name '*.css' -print 2>/dev/null
>
> Is the search not meant to be recursive by default?
>
Yes. At least GNU find is.
But I have found it to be pretty quirky.
Is the ~ there in the actual dir name? That's a special character of sorts to
the shell and other apps.
Alan
--
For Linux/Bash users: Eliminate spam with
the Mailbox-Sentry-Program. See the thread
MSP on comp.mail.misc for the scripts and docs.
- Next message: SK: "Re: How to subscribe to this news group?"
- Previous message: Lew Pitcher: "Re: Difference in mangling"
- In reply to: Lekeas GK: "Problem with the find command"
- Next in thread: Barry Margolin: "Re: Problem with the find command"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|