[Subject Prev][Subject Next][Thread Prev][Thread Next][Subject Index][Thread Index]
find command usage
Hi.
Well , AJay, i tried whatever you said. This is what I got:
find . -name "*.[ch]" -not -name "*[23]600*" >csope.file
find: bad option -not
find: path-list predicate-list
I went thro the man pages and the -not option exists. Still, this didnt
work.
I still havent been able to get a solution to that problem.
I tried the other options suggested on the list, however, they all give the
same end result.
How would I do it in more than one step, at least ? I am still waiting for a
working solution...
Harish
----- Original Message -----
From: Dwivedi Ajay kumar
To: linux-india-programmers@xxxxxxxxxxxxxxxxxxxxx
Sent: Friday, January 12, 2001 12:49 PM
Subject: Re: [LIP] find command usage
The original mail seems to be lost. so sending again.
On Thu, 11 Jan 2001, sreangsu acharyya wrote:
>
>
> I would do it this way
>
> find . -name *.[ch] | grep -v "[23]600">cscope.file
>
> I don't know whether find has a negation operator similar to grep -v, but
> i have a feeling its there, time for me to look the man pages
>
find . -name "*.[ch]" -not -name "*[23]600*" >csope.file
the double quotes being necessary to avoid expansions.
--
#!!! If anything can go wrong, _FIX_ it. (To hell with MURPHY)
Ajay kumar Dwivedi
ajayd@xxxxxxxxxx