public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "john daintree" <johnd@dyalog.com>
To: <cygwin@cygwin.com>
Subject: RE: Starting CMD from a bash shell with current directory on a mounted/network drive results in an incorrect current directory
Date: Tue, 14 Dec 2021 10:12:53 -0000	[thread overview]
Message-ID: <011c01d7f0d3$2888d220$799a7660$@dyalog.com> (raw)
In-Reply-To: <YbdhcL2vL5oL94xO@calimero.vinschen.de>

Cool, thanks.

-----Original Message-----
From: Cygwin <cygwin-bounces+johnd=dyalog.com@cygwin.com> On Behalf Of
Corinna Vinschen
Sent: 13 December 2021 15:06
To: cygwin@cygwin.com
Subject: Re: Starting CMD from a bash shell with current directory on a
mounted/network drive results in an incorrect current directory

On Dec 13 20:06, Takashi Yano wrote:
> On Mon, 13 Dec 2021 10:53:41 -0000
> "john daintree" wrote:
> > I've just upgraded a machine from Windows 10 to Windows 11. Part of 
> > my work process is now broken because when starting cmd from Cygwin 
> > with the current directory on a mounted drive I get the following
error/warning/issue:
> > 
> >  
> > 
> >  
> > 
> > /cygdrive/j$ cmd
> > 
> > '\\nas00.<redacted>\devt\users\johnd'
> > 
> > CMD.EXE was started with the above path as the current directory.
> > 
> > UNC paths are not supported.  Defaulting to Windows directory.
> > 
> > Microsoft Windows [Version 10.0.22000.348]
> > 
> > (c) Microsoft Corporation. All rights reserved.
> > 
> >  
> > 
> > C:\Windows>
> > 
> >  
> > 
> >  
> > 
> > The drive J: is mounted as something on our network (I've redacted a 
> > bit of the path, for probably no good reason)
> > 
> >  
> > 
> > Is there a workaround? Or is this something that can be fixed in Cygwin?
> 
> Thanks for the report. This was already fixed recently in git head.
> 
> https://cygwin.com/pipermail/cygwin/2021-December/250153.html
> https://cygwin.com/pipermail/cygwin-patches/2021q4/011583.html
> 
> Please wait for the next cygwin release or new developers snapshot.

New developer snapshot is available on https://cygwin.com/snapshots/


Corinna

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple


      reply	other threads:[~2021-12-14 10:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 10:53 john daintree
2021-12-13 11:06 ` Takashi Yano
2021-12-13 11:09   ` john daintree
2021-12-13 15:06   ` Corinna Vinschen
2021-12-14 10:12     ` john daintree [this message]

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='011c01d7f0d3$2888d220$799a7660$@dyalog.com' \
    --to=johnd@dyalog.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).