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
Date: Wed, 03 Oct 2001 11:40:36 -0500 (Central Daylight Time)
From: Michael Hoffman <grouse AT mail DOT utexas DOT edu>
Subject: RE: spaces in paths in bash, and the FAQ
In-reply-to: <80575AFA5F0DD31197CE00805F650D7602D020@wilber.adroit.com>
X-X-Sender: grouse AT mail DOT utexas DOT edu
To: "Robinow, David" <drobinow AT dayton DOT adroit DOT com>, John Lee <jjl AT pobox DOT com>
Cc: cygwin AT cygwin DOT com
Message-id: <Pine.WNT.4.40.0110031135520.796-100000@barbecueworld>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII

On Wed, 3 Oct 2001, Robinow, David wrote:

>  Well, you've screwed yourself by putting spaces in your path.

You could always use (e.g.) /c/progra~1/python21. Ick.

In any case, the following example will work:

$ pico=/c/Program\ Files/Pine/pico.exe
$ echo $pico
/c/Program Files/Pine/pico.exe
$ "$pico"

And pico starts up just fine.
-- 
Michael Hoffman <grouse AT mail DOT utexas DOT edu>
The University of Texas at Austin


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/