Subject: Re: CONTINUING Elementary Problems with Find
From: [email-masked] (Robert Seeger)

22 Oct 1997 20:50:12 -0700
Message-ID: <[email-masked]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: GBradfor <[email-masked]>, [email-masked]

Try:
	find . -name \*.c -print

The shell replaces *.c with all .c files in the directory. You have to use
\*.c to make the shell ignore the * character.

				Hope this helps,
				Robert Seeger

At 09:06 AM 10/22/97 -0500, GBradfor wrote:
>     Thanks to all who responded to my first post.  Yes, indeed, it was the 
>     Windows version of find that was causing my problem.  However, 
>     correcting this problem has revealed another.  Again, it is probably 
>     newbie in nature, but your assistance is appreciated.
>     
>     Taking my initial command line:
>        find . -name *.c -print
>     
>     gives the following error:
>        find:  Paths must precede expression
>        Usage:  find [path...] [expression]
>     
>     Just to check things out, I got into bash and checked my pwd 
>     (/gnu_src/cdk/winsup), and I entered this absolute address into the 
>     command line.  No luck, same error.
>     
>     Suggestions?
>     
>     Thanks again for your patience and your help.
>     
>     /s/
>     Pat Bradford
>     
>     Reply to:
>        [email-masked]
>                AND/OR
>        [email-masked]
>     
>-
>For help on using this list (especially unsubscribing), send a message to
>"[email-masked]" with one line of text: "help".
>
========================================
Robert Seeger
Network Engineer
Bay Networks

Telephone:	(518)237-2087
Pager:		(800)SKY-8888  Pin#1264792
Fax:		(518)237-4190
Email:		[email-masked]
Address:	224 5th Ave, Apt#2
		Lansingburgh, NY 12182
========================================
-
For help on using this list (especially unsubscribing), send a message to
"[email-masked]" with one line of text: "help".