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: Wed, 5 Dec 2001 11:10:41 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: cygwin 1.3.6 + bash 2.05a-2 + command completion Message-ID: <20011205111041.A12441@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com References: <3C0DE9BF.42B4B14D@uniweb.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C0DE9BF.42B4B14D@uniweb.se>; from jens@uniweb.se on Wed, Dec 05, 2001 at 10:32:47AM +0100 On Wed, Dec 05, 2001 at 10:32:47AM +0100, Yllman, Jens wrote: > Hi, > > I've hade the same problem since 1.3.6. And now I have 1.3.6-3 > installed. Still the same problem. 1.3.5 works fine. > > If you run sh instead of bash you get tab characters. So I guess it has > to do with the file find process in bash. But that has nothing to do with the Cygwin version nor with the bash version. sh in Cygwin isn't bash but ash. Ash doesn't have file completion. Just call `echo $BASH_VERSION' in the shell: In bash: $ echo $BASH_VERSION 2.05a.0(2)-release In ash == sh: $ echo $BASH_VERSION <-- Empty Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/