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

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

[Yllman, Jens]

 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
------------------------------------------------------------
Uniweb AB                            Phone:  +46 8 626 42 00
P O Box 745                          FAX:    +46 8 626 42 01
S-191 27  SOLLENTUNA
SWEDEN                               http://www.uniweb.se/

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

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

[Corinna Vinschen]

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/

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

[Robert Collins]

Chris,
    I've tracked this to having a element like
/cygdrive/s/foo where <s> does not exist in the PATH.

I don't know why that path element didn't show for cygcheck, but there
you are.

So, steps to reproduce:
export PATH=$PATH:/cygdrive/z/foo
where z: doesn't exist

Jens, 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" <jens@uniweb.se>
To: <cygwin@cygwin.com>
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. 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
> ------------------------------------------------------------
> Uniweb AB                            Phone:  +46 8 626 42 00
> P O Box 745                          FAX:    +46 8 626 42 01
> S-191 27  SOLLENTUNA
> SWEDEN                               http://www.uniweb.se/
>
> --
> 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/
>
>


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

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

[Yllman, Jens]

 Hi,

 Yes, I have a /cygdrive/x in my path that is not always maped. When I
map it it works fine.

 Small question. Is putting a directory named cygdrive in your root a
smart thing to do? It makes it possible to do 'cd /cygdrive'. But does
that make 'find / -name ...' work poor? Or is it better?

 Jens Yllman

Robert Collins wrote:
> 
> Chris,
>     I've tracked this to having a element like
> /cygdrive/s/foo where <s> does not exist in the PATH.
> 
> I don't know why that path element didn't show for cygcheck, but there
> you are.
> 
> So, steps to reproduce:
> export PATH=$PATH:/cygdrive/z/foo
> where z: doesn't exist
> 
> Jens, 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" <jens@uniweb.se>
> To: <cygwin@cygwin.com>
> 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. 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
> > ------------------------------------------------------------
> > Uniweb AB                            Phone:  +46 8 626 42 00
> > P O Box 745                          FAX:    +46 8 626 42 01
> > S-191 27  SOLLENTUNA
> > SWEDEN                               http://www.uniweb.se/
> >
> > --
> > 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/
> >
> >

-- 
------------------------------------------------------------
Uniweb AB                            Phone:  +46 8 626 42 00
P O Box 745                          FAX:    +46 8 626 42 01
S-191 27  SOLLENTUNA
SWEDEN                               http://www.uniweb.se/

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

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

[Robert Collins]

===
----- Original Message -----
From: "Yllman, Jens" <jens@uniweb.se>
> 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) to debug this myself
though.

Rob


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

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

[Yllman, Jens]

 Hi, 

 The ChangeLog reports the following.

2001-11-24  Christopher Faylor  <cgf@redhat.com>

	* 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. And I've not traced anything. Just this quick
look at the ChangeLog.

 There is also other notes about fhandler_disk_file.cc in the ChangeLog.

	* fhandler_disk_file.cc (fhandler_disk_file::opendir): Set nohandle
	flag on dummy fd.

 I don't know if anybody can look into it. I don't have any more time.

 About the reason for me testing with sh also and not only bash was to
see that it realy is bash handling of tab that crashes and not the stty
settings or something like that.

 Jens Yllman

Robert Collins wrote:
> 
> ===
> ----- Original Message -----
> From: "Yllman, Jens" <jens@uniweb.se>
> > 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) to debug this myself
> though.
> 
> Rob

-- 
------------------------------------------------------------
Uniweb AB                            Phone:  +46 8 626 42 00
P O Box 745                          FAX:    +46 8 626 42 01
S-191 27  SOLLENTUNA
SWEDEN                               http://www.uniweb.se/

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

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

[Robert Collins]

FWIW I think that cygwin is dying, not bash.

However, as I haven't looked at the code....

Rob
===
----- Original Message -----
From: "Yllman, Jens" <jens@uniweb.se>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <cygwin@cygwin.com>
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-24  Christopher Faylor  <cgf@redhat.com>
>
> * 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. And I've not traced anything. Just this quick
> look at the ChangeLog.
>
>  There is also other notes about fhandler_disk_file.cc in the
ChangeLog.
>
> * fhandler_disk_file.cc (fhandler_disk_file::opendir): Set nohandle
> flag on dummy fd.
>
>  I don't know if anybody can look into it. I don't have any more time.
>
>  About the reason for me testing with sh also and not only bash was to
> see that it realy is bash handling of tab that crashes and not the
stty
> settings or something like that.
>
>  Jens Yllman
>
> Robert Collins wrote:
> >
> > ===
> > ----- Original Message -----
> > From: "Yllman, Jens" <jens@uniweb.se>
> > > 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) to debug this myself
> > though.
> >
> > Rob
>
> --
> ------------------------------------------------------------
> Uniweb AB                            Phone:  +46 8 626 42 00
> P O Box 745                          FAX:    +46 8 626 42 01
> S-191 27  SOLLENTUNA
> SWEDEN                               http://www.uniweb.se/
>


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

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

[Christopher Faylor]

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 there will be a long thread speculating that
this has something to do with the Bermuda Triangle by the time I return.

cgf

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

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

[Yllman, Jens]

 Hi,

 I tried to take a shot at this. But I did not manage to compile the
cygwin source. I'm not sure how to do that. I also failed to compile the
cygcheck program to find a possible missfeature in that program. And at
the moment I don't have the time to find out what is going wrong with
that.

 But as has shown is that it is the traversing of the path. That is
trying to find files in paths that does not exist. I guess that it has
something to do with opendir/readdir. If I have time tonight I'll try to
compare diffrences between 1.3.5-3 and 1.3.6 source. But if I interperet
the ChangeLog correctly the changes on the opendir/readdir part is quite
large.

 Jens Yllman

Robert Collins wrote:
> 
> FWIW I think that cygwin is dying, not bash.
> 
> However, as I haven't looked at the code....
> 
> Rob
> ===
> ----- Original Message -----
> From: "Yllman, Jens" <jens@uniweb.se>
> To: "Robert Collins" <robert.collins@itdomain.com.au>
> Cc: <cygwin@cygwin.com>
> 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-24  Christopher Faylor  <cgf@redhat.com>
> >
> > * 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. And I've not traced anything. Just this quick
> > look at the ChangeLog.
> >
> >  There is also other notes about fhandler_disk_file.cc in the
> ChangeLog.
> >
> > * fhandler_disk_file.cc (fhandler_disk_file::opendir): Set nohandle
> > flag on dummy fd.
> >
> >  I don't know if anybody can look into it. I don't have any more time.
> >
> >  About the reason for me testing with sh also and not only bash was to
> > see that it realy is bash handling of tab that crashes and not the
> stty
> > settings or something like that.
> >
> >  Jens Yllman
> >
> > Robert Collins wrote:
> > >
> > > ===
> > > ----- Original Message -----
> > > From: "Yllman, Jens" <jens@uniweb.se>
> > > > 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) to debug this myself
> > > though.
> > >
> > > Rob
------------------------------------------------------------
Uniweb AB                            Phone:  +46 8 626 42 00
P O Box 745                          FAX:    +46 8 626 42 01
S-191 27  SOLLENTUNA
SWEDEN                               http://www.uniweb.se/

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

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

[Yllman, Jens]

 More information. When I have all the mounts up that's in the PATH
things work. And if you write /oll and press TAB and it matches nothing
it just works fine. BUT if you write /cygdrive/z/a and press TAB and z
does not exist, it dies.

 This is just info for anybody who is looking at this.

 Jens Yllman

Robert Collins wrote:
> 
> FWIW I think that cygwin is dying, not bash.
> 
> However, as I haven't looked at the code....
> 
> Rob
> ===
> ----- Original Message -----
> From: "Yllman, Jens" <jens@uniweb.se>
> To: "Robert Collins" <robert.collins@itdomain.com.au>
> Cc: <cygwin@cygwin.com>
> 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-24  Christopher Faylor  <cgf@redhat.com>
> >
> > * 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. And I've not traced anything. Just this quick
> > look at the ChangeLog.
> >
> >  There is also other notes about fhandler_disk_file.cc in the
> ChangeLog.
> >
> > * fhandler_disk_file.cc (fhandler_disk_file::opendir): Set nohandle
> > flag on dummy fd.
> >
> >  I don't know if anybody can look into it. I don't have any more time.
> >
> >  About the reason for me testing with sh also and not only bash was to
> > see that it realy is bash handling of tab that crashes and not the
> stty
> > settings or something like that.
> >
> >  Jens Yllman
> >
> > Robert Collins wrote:
> > >
> > > ===
> > > ----- Original Message -----
> > > From: "Yllman, Jens" <jens@uniweb.se>
> > > > 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) to debug this myself
> > > though.
> > >
> > > Rob
> >
> > --
> > ------------------------------------------------------------
> > Uniweb AB                            Phone:  +46 8 626 42 00
> > P O Box 745                          FAX:    +46 8 626 42 01
> > S-191 27  SOLLENTUNA
> > SWEDEN                               http://www.uniweb.se/
> >

-- 
------------------------------------------------------------
Uniweb AB                            Phone:  +46 8 626 42 00
P O Box 745                          FAX:    +46 8 626 42 01
S-191 27  SOLLENTUNA
SWEDEN                               http://www.uniweb.se/

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