From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: unzip, find broken by auto handling of .exe file extension
Date: Tue, 13 Sep 2016 08:00:00 -0000 [thread overview]
Message-ID: <6834a8ba-8dc9-28f2-38b7-08fef186edb7@gmail.com> (raw)
In-Reply-To: <F4E41EBA-31C7-42F7-BDDB-2DFE840B092B@gmail.com>
On 13/09/2016 01:30, Stephen Anderson wrote:
>
>>
>> This characteristics is needed as windows for historical reason
>> requested ".exe" extension for all executable files, while
>> Unix have not such restriction.
>>
>> So "cat.exe" is recognized by cygwin also as "cat".
>> Without this feature all scripts taken by traditional Unix's will
>> be broken and cygwin will be unusable.
>>
>> Try this experiment on Linux:
>>
>> touch foo
>> mkdir foo
>>
>> does it work ?
>
> This is not relevant, there is no foo, there is only foo.exe.
foo.exe is also foo for cygwin .
It seems you have problem to understand it
>
> In the case of windows _command_ processing, certain extensions are searched for automatically without creating an equivalency in file names. This means that for the same directory and filename hierarchy, windows and linux archive processing work, cygwin uniquely fails. Not a desirable outcome.
>
> IMHO the only time cygwin should be looking for .exe (or .cmd, .bat etc if desired), is when no match is found on loading a _command_, possibly only from a shell.
Feel free to provide a patch to solve it, but I suspect your solution
will be worst then current implementation.
There is no way to predict if the search for a file will be used to run
it afterwards, so breaking functional scripts or programs.
> sja
Regards
Marco
--
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
prev parent reply other threads:[~2016-09-13 5:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 16:00 Stephen Anderson
2016-09-02 18:40 ` cyg Simple
2016-09-02 20:20 ` Stephen Anderson
2016-09-09 13:18 ` Stephen Anderson
2016-09-09 13:59 ` Nellis, Kenneth
2016-09-12 20:37 ` Stephen Anderson
2016-09-12 23:30 ` Marco Atzeri
2016-09-12 23:41 ` Stephen Anderson
2016-09-13 1:35 ` Andy Hall
2016-09-13 8:00 ` Marco Atzeri [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=6834a8ba-8dc9-28f2-38b7-08fef186edb7@gmail.com \
--to=marco.atzeri@gmail.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).