public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "John Gibb" <jgibb1@ix.netcom.com>
To: "GBradfor" <GBradfor@fhssmtp.redstone.army.mil>, <gnu-win32@cygnus.com>
Subject: Re: Elementary Problem with find
Date: Tue, 21 Oct 1997 18:19:00 -0000	[thread overview]
Message-ID: <01bcde88$284154e0$609b5dcf@pentium> (raw)

I suspect you are using the wrong 'find'.  For example, i found myself
inadvertently using the NT flavor of find instead of the bash flavor...turns
out my PATH had /WINNT/systemm32 prior to /gnuwin32/../bin.

I created the following alias to combat this:

alias f='//D/gnuwin32/b18/H-i386-cygwin32/bin/find.exe'

John Gibb
(415)-584-3754
jgibb1@ix.netcom.com
-----Original Message-----
From: GBradfor <GBradfor@fhssmtp.redstone.army.mil>
To: gnu-win32@cygnus.com <gnu-win32@cygnus.com>
Date: Tuesday, October 21, 1997 5:35 PM
Subject: Elementary Problem with find


>     This is, more than likely, a true newbie problem.  I've searched the
>     back issues of the mailing list, and there are no other reports of
>     this problem.  So, it's probably just me; but just in case...
>
>     find is failing to take valid command strings.  I am running b18 under
>     Windows95.
>
>     Example case:
>        find . -name *.c -print
>
>     The cygwin32 version gives the following error:
>        FIND:  Parameter format not correct
>
>     Running this same command on my Linux box gives the appropriate file
>     listing.
>
>     I have also tried variations on this same theme:
>        find <absolute path name (with both '\' and '/')> -name *.c -print
>        find -name *.c -print     /* no starting pathname; use present */
>                                  /* directory as default.             */
>        find . -name "*.c" -print
>        find . -name '*.c' -print
>
>     The most interesting was:
>        find "<absolute pathname>" -name *.c -print
>     find ignored what was in quotes and interpretted everything else as
>     search paths.
>
>     Any suggestions on this?
>
>     /s/
>     Pat Bradford
>
>     Reply to:
>     gbradfor@redstone.army.mil
>          AND/OR
>     p_n_brad@traveller.com
>-
>For help on using this list (especially unsubscribing), send a message to
>"gnu-win32-request@cygnus.com" with one line of text: "help".
>

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1997-10-21 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-21 18:19 John Gibb [this message]
1997-10-22  4:14 ` Paul Kirkaas
  -- strict thread matches above, loose matches on Subject: below --
1997-10-22 20:41 raf
1997-10-23  2:21 ` Tage Westlund
1997-10-25 12:17   ` Michael Hirmke
1997-10-22  6:38 Larry Hall
1997-10-21 23:17 Sergey Okhapkin
1997-10-21 14:54 GBradfor
1997-10-22  1:08 ` Claus Brod

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='01bcde88$284154e0$609b5dcf@pentium' \
    --to=jgibb1@ix.netcom.com \
    --cc=GBradfor@fhssmtp.redstone.army.mil \
    --cc=gnu-win32@cygnus.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).