* Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2
@ 2021-11-17 14:41 Wolfgang S. Kechel
2021-11-17 16:44 ` Andrey Repin
0 siblings, 1 reply; 3+ messages in thread
From: Wolfgang S. Kechel @ 2021-11-17 14:41 UTC (permalink / raw)
To: cygwin; +Cc: support, PRS Sysadm, Adrián Medraño Calvo
Dear folks!
The command 'cygpath -am .' yields different results between
cygwin-3.1.4-1 and cygwin-3.3.2-1 on a Windows 10 box when the current
directory is a network share.
Example with V3.1.4:
cygpath -am . ---> P:/mytool/gbuild/wintel/libtiff
Example with V3.3.2-1
cygpath -am . ---> //mynas.mydomain.de/product/mytool/gbuild/wintel/libtiff
This causes UNC filenames to appear and this cmd.exe is unable to start
in those directories when started from a cygwin shell or from nmake run
in a cygwin shell.
I prefer to get the old behaviour back since it worked for 20+ years up
to now - or at least an option to enable the old behavior again.
Please note that I have not subscribed to any cygwin mailing list.
Thanks in advance and best regards
Wolfgang
--
Wolfgang Kechel mailto:wolfgang.kechel@prs.de
Patzschke + Rasp Software GmbH http://www.prs.de
Bierstadter Straße 7 Fax: +49-(0)611-1731-31
D-65189 Wiesbaden Phone: +49-(0)611-1731-611 / +49-(0)174-3454260
Patzschke + Rasp Software GmbH, Bierstadter Str. 7, D-65189 Wiesbaden
Eintragung im Handelsregister: Amtsgericht Wiesbaden, HRB Nr. 22673
Geschäftsführer: Wolfgang Kechel, Till Immanuel Patzschke
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2
2021-11-17 14:41 Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2 Wolfgang S. Kechel
@ 2021-11-17 16:44 ` Andrey Repin
2021-11-17 18:29 ` Corinna Vinschen
0 siblings, 1 reply; 3+ messages in thread
From: Andrey Repin @ 2021-11-17 16:44 UTC (permalink / raw)
To: Wolfgang S. Kechel, cygwin
Greetings, Wolfgang S. Kechel!
> The command 'cygpath -am .' yields different results between
> cygwin-3.1.4-1 and cygwin-3.3.2-1 on a Windows 10 box when the current
> directory is a network share.
> Example with V3.1.4:
> cygpath -am . ---> P:/mytool/gbuild/wintel/libtiff
> Example with V3.3.2-1
> cygpath -am . ---> //mynas.mydomain.de/product/mytool/gbuild/wintel/libtiff
I'm pretty sure there was a discussion about it earlier.
> This causes UNC filenames to appear and this cmd.exe is unable to start
> in those directories when started from a cygwin shell or from nmake run
> in a cygwin shell.
cmd.exe can be configured to STFU.
>> $ cd $( cygpath -am . )
>>
>> $ cmd /C DIR .
>> Volume in drive \\DAEMON1\anrdaemon is anrdaemon
>> Volume Serial Number is 3D5A-4F9A
>>
>> Directory of \\DAEMON1\anrdaemon\Documents\_ps1
>>
>> 22.07.2020 10:23 <DIR> .
>> 27.07.2021 19:21 <DIR> ..
>> 28.08.2019 14:25 <DIR> HTML5Video
>> 22.03.2020 00:22 <DIR> Maintenance
>> 22.03.2020 00:23 88 wmi.btm
>> 29.08.2018 18:14 1 871 dl-files.cmd
>> 01.09.2019 18:01 194 ats.sh
>> 3 File(s) 2 153 bytes
>> 4 Dir(s) 361 313 710 080 bytes free
>>
>> $
> I prefer to get the old behaviour back since it worked for 20+ years up
> to now - or at least an option to enable the old behavior again.
The option is in https://ss64.com/nt/syntax-cmd.html (Original article from
web archive:
https://web.archive.org/web/20150312195558/https://support.microsoft.com/en-us/kb/156276
)
> Please note that I have not subscribed to any cygwin mailing list.
Noted…
--
With best regards,
Andrey Repin
Wednesday, November 17, 2021 19:36:02
Sorry for my terrible english...
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2
2021-11-17 16:44 ` Andrey Repin
@ 2021-11-17 18:29 ` Corinna Vinschen
0 siblings, 0 replies; 3+ messages in thread
From: Corinna Vinschen @ 2021-11-17 18:29 UTC (permalink / raw)
To: cygwin
On Nov 17 19:44, Andrey Repin via Cygwin wrote:
> Greetings, Wolfgang S. Kechel!
>
> > The command 'cygpath -am .' yields different results between
> > cygwin-3.1.4-1 and cygwin-3.3.2-1 on a Windows 10 box when the current
> > directory is a network share.
>
> > Example with V3.1.4:
>
> > cygpath -am . ---> P:/mytool/gbuild/wintel/libtiff
>
> > Example with V3.3.2-1
>
> > cygpath -am . ---> //mynas.mydomain.de/product/mytool/gbuild/wintel/libtiff
>
> I'm pretty sure there was a discussion about it earlier.
>
> > This causes UNC filenames to appear and this cmd.exe is unable to start
> > in those directories when started from a cygwin shell or from nmake run
> > in a cygwin shell.
>
> cmd.exe can be configured to STFU.
Apparently default starting with Windows 11...
Corinna
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-11-17 18:29 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-11-17 14:41 Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2 Wolfgang S. Kechel
2021-11-17 16:44 ` Andrey Repin
2021-11-17 18:29 ` Corinna Vinschen
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).