This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 'cp' utility bug when <dest-name>.exe file exist.
Why not just do the exe magic for executing the files only? When
opening, stating, copying, moving etc, you could leave it out. This
seems the most reasonable compromise to me, but there could of course
be cases which I am overseeing, but I wouldn't expect any script to
rely on exe magic when opening a file for editing.
On 6/9/10, Andy Koppe <andy.koppe@gmail.com> wrote:
> On 9 June 2010 10:48, Julio Costa wrote:
>>>>And this is where my head got reeeally spinning... can anyone, please,
>>>>explain the reason to why this .exe magic exists, anyway?
>
> As far as I understand it, the original reason for it was that Windows
> 9x always required it. Of course Cygwin 1.7 no longer supports 9x, so
> from that perspective, it's no longer needed.
>
>
>>> [Running in cmd.exe]
>> The point is, that *is not* a reason, because it is easily fixed by
>> "set PATHEXE=%PATHEXE%:.".
>
> That's a nice one. I certainly didn't know about that.
>
> Explorer still needs the .exe though. More importantly, a lot of build
> scripts likely depend on the .exe being added automatically.
>
> The frequent questions and problems around this issue do make me
> wonder though whether it wouldn't indeed be better to drop the .exe
> magic completely, deal with the ensuing pain, but eventually be done
> with it.
>
> Andy
>
> --
> 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
>
>
--
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