Re: 'cp' utility bug when <dest-name>.exe file exist.

[Andy Koppe <andy dot koppe at gmail dot com>]

On 9 June 2010 14:50, Julio Costa wrote:
>>>> [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.
>
> Nope also.
> Try this at a cmd.exe:
>
> D:\ETC\Tools>assoc .=MyDefaultLauncher
> .=MyDefaultLauncher
>
> D:\ETC\Tools>ftype MyDefaultLauncher=%COMSPEC% /C "%1"
> MyDefaultLauncher=C:\WINDOWS\system32\cmd.exe /C "%1"
>
> D:\ETC\Tools>regtool set "/user/Software/Microsoft/Command
> Processor/AutoRun" 'set PATHEXT=%PATHEXT%;.'

Or just:

assoc .=exefile

Hmm, interesting.


>> More importantly, a lot of build scripts likely depend on the .exe being added automatically.
>
> Hm. Maybe they shouldn't.

Yeah, but "shouldn't" never stopped anyone, hence any transition would
certainly not be pain-free.

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