public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash
Date: Fri, 05 Mar 2010 15:33:00 -0000	[thread overview]
Message-ID: <20100305152637.GK7980@calimero.vinschen.de> (raw)
In-Reply-To: <4B91105B.7050205@sidefx.com>

On Mar  5 09:08, Edward Lam wrote:
> 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.

Is that a case-sensitivity issue, perhaps?  See
http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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

  reply	other threads:[~2010-03-05 15:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 15:36 Eric Blake
2009-07-14 15:36 ` GOLD STAR! (was Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash) Corinna Vinschen
2010-01-21 15:01 ` [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash Edward Lam
2010-01-21 16:03   ` Christopher Faylor
2010-01-22  4:15   ` Eric Blake
2010-03-05 14:11     ` Edward Lam
2010-03-05 15:33       ` Corinna Vinschen [this message]
2010-03-05 17:00         ` Edward Lam
2010-03-05 17:01           ` Edward Lam
2010-03-05 17:06             ` Edward Lam
2010-03-05 17:20           ` Eric Blake
2010-03-05 17:40             ` Corinna Vinschen
2010-03-05 20:11               ` Edward Lam
2011-12-03 22:11               ` Eric Blake
2013-03-28 15:08                 ` [PATCH] Support DOS paths in dash Edward Lam
2010-03-05 17:10         ` [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash Edward Lam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100305152637.GK7980@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).