X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=BMZt7tymWxcfYbE7
	eNmo4oGyI1Fkhioa3CgbtXq5UTUsiSdZ6rWK5N2chgLYJc9pWyk2rNx6cayTKYK1
	sbbvbWlfsOmTiNgrkZviAwQ+yMJb8ixOe6OZM/EdkJAoXpRQk9yIx25lx3qxRcHM
	i/bzCKzbmT6i+GNjazZgpbcssX0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=i8eDF7DnpFayY2KPK6JOet
	P2XrA=; b=ViAi2u8xoqhEmzBZRmhvSO7sSjYMEyV+4VtxiTp+P9q0sLO7ctdSnq
	l5BK1cMdl49RNtu9an1BBGbufdI0ZVMYmwWKzlvM2onQOpWLyr6741bal0uWHB1A
	Aaw8ZZnChHD4HLHveFcIKB6uidst7TkW8ddHhcbsjCRK/Le+Dm4j4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.6 required=5.0 tests=AWL,BAYES_50,RDNS_NONE autolearn=no version=3.3.2
X-HELO: vms173023pub.verizon.net
Message-id: <5296644F.306@cygwin.com>
Date: Wed, 27 Nov 2013 16:29:51 -0500
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
Reply-to: cygwin@cygwin.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-version: 1.0
To: cygwin@cygwin.com
Subject: Re: Path issue with windows shell
References: <029801ceebab$c5a6eff0$50f4cfd0$@subrigo.net> <52965393.80307@cygwin.com> <02d901ceebb3$e34e0ea0$a9ea2be0$@subrigo.net>
In-reply-to: <02d901ceebb3$e34e0ea0$a9ea2be0$@subrigo.net>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 11/27/2013 4:01 PM, Matthew Lagoe wrote:
> Sorry I did not clarify earlier, I have cygin added to my path and I have
> not added anything to /cygdrive or otherwise.
>
> C:\tmp>where ls
> C:\cygwin\bin\ls.exe
>
> C:\tmp>C:\cygwin\bin\ls.exe /cygdrive
> c
>
>
> I noticed that all the paths that I am having issues with are setup via a
> "subst" in windows
>
> You can reproduce this problem easily by following these steps
>
>>From the windows cmd.exe shell type
>
> subst R: C:\tmp
>
> This will create a new drive "R" that will point to C:\tmp
>
> In the windows cmd.exe shell type C:\cygwin\bin\ls.exe /cygdrive you will
> see your C drive but no R drive
>
> Open the Cygwin shell
>
> Type ls /cygdrive and you will see both C and R
>
>
> I also attached the cygcheck.out to this email as requested.

Thanks.  I don't see anything obvious there.  I tried reproducing
your problem on 3 machines I have here, 2 at 1.7.25 and 1 at 1.7.17.
They all showed all the drives, including the subst'd drive, in
both Cygwin and outside.  I'm not sure why you're seeing what you're
seeing.  Perhaps if you look at the output of strace when
running from cmd.exe outside of bash, this will shed some light on
why R is being ignored?


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

