Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<E1B42CFD544FD31193EE0000E87C5CE7E07E82@mailserver2.mqsoftware.com>
From:	Glen Coakley <gcoakley AT mqsoftware DOT com>
To:	"'Cygwin Users'" <cygwin AT cygwin DOT com>
Subject:	RE: Bash syntax with native NT commands
Date:	Mon, 4 Jun 2001 10:57:38 -0500
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)

> Earl wrote:
> > 
> > Is there a general set of rules to describe how to quote 
> properly bash
> > syntax with regard to native NT commands and fileystem?
> > 
> > For example, I'm trying to get the NT command FIND to work 
> within BASH:
> > 
> 
> First, let me caution that there exists a UNIX style `find' executable
> your /bin directory also.
> 
> > find /I "text" \\ server\c$\textfile.txt
> > 
> 
> cmd /c find /I "text' \\\\server\\c$\\textfile.txt

I think you meant:

  cmd /c find /I "text" \\\\server\\c$\\textfile.txt

Notice the second double quote.
 
Personally, I find the /bin/find syntax much saner.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -