Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	Fri, 28 Feb 2003 22:14:48 -0500
From:	"Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>
To:	cygwin AT cygwin DOT com
Subject:	Re: bash's (built-in) type command can not handle spaces in paths
Message-ID:	<20030301031448.GA49737955@hpn5170x>
Mail-Followup-To:	"Pierre A. Humblet" <pierre DOT humblet AT ieee DOT org>,
	cygwin AT cygwin DOT com
References:	<5 DOT 2 DOT 0 DOT 9 DOT 0 DOT 20030228163559 DOT 073b84f0 AT mail DOT real DOT com>
Mime-Version:	1.0
In-Reply-To:	<5.2.0.9.0.20030228163559.073b84f0@mail.real.com>
User-Agent:	Mutt/1.4i

On Fri, Feb 28, 2003 at 04:42:53PM -0800, Curtis Siemens wrote:
> 
> By the way, given that I can actually run an executable that bash/type
> can't find, does this suggest that possibly the builtin type command
> is doing something wrong?

Yes and no. Obviously it isn't working as it should. But in bash's defense 
there is not a single POSIX call it could use to find out what your actual
access rights are, on systems that don't use the traditional permissions.
However "access" comes close.
The problem is being addressed and will be solved perfectly (time will tell !)
soon.

Pierre

--
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/

- Raw text -