This is the mail archive of the
mailing list for the Cygwin project.
Re: How does Cygwin determine PWD
- From: Wayne Johnson <wdtj at yahoo dot com>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Mon, 30 Sep 2013 09:14:24 -0700 (PDT)
- Subject: Re: How does Cygwin determine PWD
- Authentication-results: sourceware.org; auth=none
- References: <1380557054 dot 49989 dot YahooMailNeo at web121506 dot mail dot ne1 dot yahoo dot com>
- Reply-to: Wayne Johnson <wdtj at yahoo dot com>
I am upgrading some of our scripts to use the latest version of Cygwin bash et. al. and run into an interesting problem that I'm having trouble explaining.
I have put bash, pwd, etc. into a directory called support_tools, and have a batch file that does a cd to the support_tools directory and then runs bash in order to capture some information.
In the old version of bash (3.2.49(22)) when we run bash, pwd returns the proper cygwinified path, like C:\Program Files (x86)\install_dir\support_tools.
Under the new bash (4.1.10(4)), when I do pwd I get /support_tools.
How does bash (or in this case probably one of the cygwin libraries) determine the current directory when you start it up?
There are two kinds of people: Those who say to God, "Thy will be done," and those to whom God says, "All right, then, have it your way." --C.S. Lewis
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple