Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

Collins" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, December 05, 2001 11:39 PM > Subject: Re: cygwin 1.3.6 + bash 2.05a-2 + command completion > > > Hi, > > > > The ChangeLog reports the following. > > > > 2001-11-2

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

; From: "Yllman, Jens" <[EMAIL PROTECTED]> > To: "Robert Collins" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, December 05, 2001 11:39 PM > Subject: Re: cygwin 1.3.6 + bash 2.05a-2 + command completion > > > H

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

On Wed, Dec 05, 2001 at 11:49:25PM +1100, Robert Collins wrote: >FWIW I think that cygwin is dying, not bash. > >However, as I haven't looked at the code ...and no one else will, of course. I'm going to be inaccessible for a couple of days. I fully expect that either Corinna will fix it or

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

day, December 05, 2001 11:39 PM Subject: Re: cygwin 1.3.6 + bash 2.05a-2 + command completion > Hi, > > The ChangeLog reports the following. > > 2001-11-24 Christopher Faylor <[EMAIL PROTECTED]> > > * fhandler_disk_file.cc (fhandler_cygdrive::readdir): Avoid reporting >

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

Hi, The ChangeLog reports the following. 2001-11-24 Christopher Faylor <[EMAIL PROTECTED]> * fhandler_disk_file.cc (fhandler_cygdrive::readdir): Avoid reporting inaccessible drives. Maybe bash expect to get something like invalid drive or something. I've not checked bash.

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

=== - Original Message - From: "Yllman, Jens" <[EMAIL PROTECTED]> > Hi, > > Yes, I have a /cygdrive/x in my path that is not always maped. When I > map it it works fine. Ok, in my mind that conforms the way to reproduce. I don't have time at the moment (sigh, I wish I did, I really do)

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

From: "Yllman, Jens" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, December 05, 2001 8:32 PM > Subject: Re: cygwin 1.3.6 + bash 2.05a-2 + command completion > > > Hi, > > > > I've hade the same problem since 1.3.6. An

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

, can you check your path within bash (set | grep PATH) and see if you have any non-existant drive letters listed? Rob === - Original Message - From: "Yllman, Jens" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 05, 2001 8:32 PM Subject: Re: cygwin

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

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

Re: cygwin 1.3.6 + bash 2.05a-2 + command completion

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. Jens Yllman -

Re: bugreport: cygwin 1.3.6 + bash 2.05a-2 + command completion

On Tue, Dec 04, 2001 at 10:13:50AM +1100, Robert Collins wrote: >I just updated cygwin and bash. For some reason TAB command completion >is now broken. > >The symptoms are: >type a command prefix - say "ssh-ad" >hit TAB >watch the window disappear. (I'm running bash in a cmd window on Windows >XP

bugreport: cygwin 1.3.6 + bash 2.05a-2 + command completion

I just updated cygwin and bash. For some reason TAB command completion is now broken. The symptoms are: type a command prefix - say "ssh-ad" hit TAB watch the window disappear. (I'm running bash in a cmd window on Windows XP Pro). I've no further info at this point, so you can consider this a he