Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 28 Sep 2004 17:53:46 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: "which" command does not expand "~" in path (base-files update needed) Message-ID: <20040928215346.GC2242@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040928194018 DOT GR26145 AT trixie DOT casa DOT cgf DOT cx> <20040928194740 DOT GT26145 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Sep 28, 2004 at 03:48:12PM -0400, Igor Pechtchanski wrote: >On Tue, 28 Sep 2004, Christopher Faylor wrote: > >> On Tue, Sep 28, 2004 at 02:43:38PM -0500, Brian Ford wrote: >> >On Tue, 28 Sep 2004, Christopher Faylor wrote: >> > >> >> Of course there is a simple solution: lose the quotes. AFAICT, they >> >> aren't needed. >> > >> >IMHO, they are. Windows programs often put directories containing spaces >> >in the system path. ex: >> > >> >/cygdrive/c/Program Files/ATI Technologies/ATI Control Panel >> >> Try the above with a PATH that contains spaces. Spaces are preserved. > >They are in this case, but won't be in general. E.g., try > >PATH=~/bin:$PATH which ls This works fine no matter where I put the directory with spaces in it. Regardless, I don't see any reason to turn this thread into an exposition on what does or doesn't work with variables that contain spaces. Dropping the quotes from the original example will just cause everything to work correctly everywhere. John Morrison, would you mind doing this, please? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/