Re: Unexpected behavior of ~ when calling bash from a different cygwin installation

2018-06-16 Thread cyg Simple
On 6/16/2018 9:33 AM, Soegtrop, Michael wrote: > Dear Marco, > >> this is due to the preference given by Windows to load dll's from the same >> directory where the program is resident instead of using the ones in the PATH > > yes, this is expected behavior. What is not expected is that the locati

RE: Unexpected behavior of ~ when calling bash from a different cygwin installation

2018-06-16 Thread Soegtrop, Michael
Dear Marco, > this is due to the preference given by Windows to load dll's from the same > directory where the program is resident instead of using the ones in the PATH yes, this is expected behavior. What is not expected is that the location of the system root in the Windows file system does no

Re: Unexpected behavior of ~ when calling bash from a different cygwin installation

2018-06-16 Thread Marco Atzeri
On 6/15/2018 3:32 PM, Soegtrop, Michael wrote: Dear Cygwin Users, I got it, I just have to clear the HOME variable before. But I have a few more observations on this: the FAQ (section 4.20) state that the root path for the mount table depends on the path of the cygwin1.dll, to which an execut

RE: Unexpected behavior of ~ when calling bash from a different cygwin installation

2018-06-16 Thread Soegtrop, Michael
Dear Andrey, > The mapping is consistent throughout the execution tree. I would like to understand the underlying mechanism. The documentation (FAQ section 4.20) states (as far as I understand) that the Windows path of the Cygwin system root an executable sees is the parent directory of the fol

Re: Unexpected behavior of ~ when calling bash from a different cygwin installation

2018-06-15 Thread Andrey Repin
Greetings, Soegtrop, Michael! > I got it, I just have to clear the HOME variable before. > But I have a few more observations on this: > the FAQ (section 4.20) state that the root path for the mount table depends > on the path of the cygwin1.dll, to which an executable is linked. "Linked" in th

RE: Unexpected behavior of ~ when calling bash from a different cygwin installation

2018-06-15 Thread Soegtrop, Michael
Dear Cygwin Users, I got it, I just have to clear the HOME variable before. But I have a few more observations on this: the FAQ (section 4.20) state that the root path for the mount table depends on the path of the cygwin1.dll, to which an executable is linked. This doesn't seem to be the case

Unexpected behavior of ~ when calling bash from a different cygwin installation

2018-06-15 Thread Soegtrop, Michael
Dear Cygwin users, I have several Cygwin installation for different purposes (think of it as light weight VMs). I observe an unexpected behavior of ~ when I call a bash from one Cygwin from a bash of another Cygwin. The procedure is as follows: *I have a Cygwin in C:\bin\cygwinA *