Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 28 Feb 2003 22:14:48 -0500 From: "Pierre A. Humblet" To: cygwin@cygwin.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" , cygwin@cygwin.com References: <5.2.0.9.0.20030228163559.073b84f0@mail.real.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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/