|
From: | Lubos Pintes |
Subject: | Re: [h-e-w] M-x ansi-term error |
Date: | Tue, 4 Apr 2017 19:09:28 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
Hello, The file name is perfectly valid. From *scratch* buffer:(file-exists-p "C:/c/emacs/libexec/emacs/25.1/i686-w64-mingw32/cmdproxy.exe")
tI have a folder named "c" on my "C:" drive. I am backing up everything contained in that folder. Thus the path could look weird to you, but it is perfectly valid. I am developing an Emacspeak server for Windows which will use SAPI voices, thus I am starting Emacs from the batch file with the following contents:
@echo off set HOME=%~dp0%home set DTK_PROGRAM=essapi %~dp0%\bin\runemacs.exe Obviously the batch file is under emacs "root directory" If I run the emacs with "-q" parameter, I receive the same error. Dňa 4. 4. 2017 o 16:32 Eli Zaretskii napísal(a):
From: Lubos Pintes <address@hidden> Date: Tue, 4 Apr 2017 12:18:09 +0200 I am trying to run a MSYS2 shell, bash.exe, under Emacs version 25.1. It offers me the path: c:/msys64/usr/bin/bash.exe This is correct path, the bash.exe is there. But after I press a RET an error Spawning child process: Invalid argument This error also appears when I try to run the default program offered by Emacs: C:/c/emacs/libexec/emacs/25.1/i686-w64-mingw32/cmdproxy.exe"C:/c/emacs/libexec/emacs/25.1/i686-w64-mingw32/cmdproxy.exe" is clearly an invalid file name. How did you start Emacs? From a desktop shortcut, from a shell prompt (and then which shell), in some other manner? Also, does the problem happen in "emacs -Q"?
[Prev in Thread] | Current Thread | [Next in Thread] |