This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash
- From: Edward Lam <edward at sidefx dot com>
- To: Eric Blake <ebb9 at byu dot net>
- Cc: cygwin at cygwin dot com
- Date: Fri, 05 Mar 2010 09:08:27 -0500
- Subject: Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash
- References: <announce.4A5C7A2B.4020700@byu.net> <4B5860C9.50100@sidefx.com> <4B591221.10501@byu.net>
Eric Blake wrote:
According to Edward Lam on 1/21/2010 7:12 AM:
DOS file paths and dash seems to NOT support them
Huh? Give an example. dash supports DOS paths the same as bash. That
is, if the : doesn't already cause other problems (as in tar), then the
DOS path is handed on to native windows (and you get the nodosfiles
warning from cygwin1.dll on the first use).
Sorry for the slow reply on this one as I had just given up and gone
from sh to bash. Here's a reproducible case (starting with bash as the
initial shell).
$ cygcheck -c cygwin dash bash
Cygwin Package Information
Package Version Status
bash 3.2.49-23 OK
cygwin 1.7.1-1 OK
dash 0.5.5.1-2 OK
$ echo $CYGWIN
nodosfilewarning
$ bash
$ cd c:/
$ pwd
/c
$ export FOO=c:/windows
$ cd $FOO
$ pwd
/c/windows
$ cd c:/
$ pwd
/c
$ dash
$ export FOO=c:/windows
$ cd $FOO
cd: 2: can't cd to c:/windows
$ exit
We rely on being able to perform "cd $FOO" where FOO is a DOS file path
and this used to work in the old ash.
Regards,
-Edward
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple