[debbugs-tracker] bug#21323: closed (start-process rejects .com executables)

[GNU bug Tracking System]

Your message dated Sat, 22 Aug 2015 22:21:39 +0300
with message-id <address@hidden>
and subject line Re: bug#21323: start-process rejects .com executables
has caused the debbugs.gnu.org bug report #21323,
regarding start-process rejects .com executables
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
21323: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21323
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> start-process rejects .com executables
>
>
>
>
> Date: 
>
> Sat, 22 Aug 2015 19:24:00 +0200
>
>
>
>
> I found this bug on windows ver 24.5.1. If you try to run a .com file:
>
> (start-process "X" "Y" "c:/Windows/System32/tree.com")
>
> You get: "Spawning child process: exec format error"
>
> The cryptic error appears to be a result of the .com extension. IIRC
> it worked in 23.x so this problem is a regression.
>
>
> -- 
> mvh/best regards Björn Lindqvist
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#21323: start-process rejects .com executables
>
>
>
>
> Date: 
>
> Sat, 22 Aug 2015 22:21:39 +0300
>
>
>
>
> > Date: Sat, 22 Aug 2015 19:24:00 +0200
> > From: Björn Lindqvist <address@hidden>
> > 
> > I found this bug on windows ver 24.5.1. If you try to run a .com file:
> > 
> > (start-process "X" "Y" "c:/Windows/System32/tree.com")
> > 
> > You get: "Spawning child process: exec format error"
>
> Indeed.
>
> > The cryptic error appears to be a result of the .com extension.
>
> No, it's because .com programs are run via cmdproxy.exe, and there's a
> bug in computing the directory where we look for it.
>
> As a workaround, you can set CMDPROXY in the environment to point to
> cmdproxy.exe (should be in libexec/emacs/24.5/i686-pc-mingw32/
> subdirectory of the directory where you installed Emacs 24.5).
>
> I've now fixed this for the next release so it will work even without
> setting CMDPROXY in the environment.  Thanks.
>
>
> --- End Message ---