public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Corner-case bug in .exe handling?
Date: Wed, 20 Mar 2019 09:24:00 -0000	[thread overview]
Message-ID: <20190320092421.GR3908@calimero.vinschen.de> (raw)
In-Reply-To: <5400e6ecebaa25efa46f0011be3fc58b58c4a69c.camel@cygwin.com>

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

On Mar 19 18:02, Yaakov Selkowitz wrote:
> Just came across this with 3.0.4 on both Win7 and Win10 1804:
> 
> $ ls -1 /usr/bin/python2.7
> /usr/bin/python2.7
> $ ls -1 /usr/bin/python[2-9].[0-9]
> /usr/bin/python3.5
> /usr/bin/python3.6
> /usr/bin/python3.7
> /usr/bin/python3.8
> 
> python2.7 is the actual .exe where python3.* are symlinks, but
> shouldn't 2.7 still be included in the latter?

No, even if that looks weird.  But think about what happens.  ls calls
readddir.  readdir returns "python2.7.exe".  The matching is not done by
Cygwin, but by the shell.  And python2.7.exe simply doesn't match
"python[2-9].[0-9]".

Nothing Cygwin can do about, unless we suppress the .exe suffix in
readdir/realpath/readlink output just like we do with the ".lnk" suffix
for the old winsymlink symlink style.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2019-03-20  9:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 22:02 Yaakov Selkowitz
2019-03-20  1:11 ` Brian Inglis
2019-03-20  9:24 ` Corinna Vinschen [this message]
2019-03-20 18:55   ` Brian Inglis
2019-03-21 12:07     ` Corinna Vinschen

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=20190320092421.GR3908@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).