Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 12 Feb 2002 12:33:47 -0500 From: Jason Tishler Subject: Re: bash 2.05a command completion spec bug In-reply-to: <005201c1b3e2$5c007840$9d00a8c0@mchasecompaq> To: Michael A Chase Cc: Cygwin Mail-followup-to: Michael A Chase , Cygwin Message-id: <20020212173347.GD1248@dothill.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.3.24i References: <20020212142928.GB1248@dothill.com> <005201c1b3e2$5c007840$9d00a8c0@mchasecompaq> Michael, On Tue, Feb 12, 2002 at 08:26:55AM -0800, Michael A Chase wrote: > Could you have a development version of cygwin1.dll somewhere in $PATH? Nope: $ which -a cygwin1.dll /usr/bin/cygwin1.dll A Windows search comes up empty too. Like I said in my previous post, the Cygwin problem is corrected when all processes have exited. Actually, I only noticed the Cygwin problem when I was writing up the bash problem. Nevertheless, bash 2.05a (at least the Cygwin version) has issues with command completion specs. Jason -- 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/