Yes, that's true. I am trying to run a MSYS2 shell under Windows.
Of course it can be run, but it generates some fancy characters like
[;32xxx] etc.
So my attempt was just an experiment "are those fancy characters ANSI
sequences mentioned elsewhere?".
So I tried the ansi-term command.
Dňa 4. 4. 2017 o 19:32 Eli Zaretskii napísal(a):
From: Lubos Pintes <lubos.pin...@gmail.com>
Date: Tue, 4 Apr 2017 19:09:28 +0200
The file name is perfectly valid. From *scratch* buffer:
(file-exists-p
"C:/c/emacs/libexec/emacs/25.1/i686-w64-mingw32/cmdproxy.exe")
t
I 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"
Thanks.
It looks like I've missed the important clue: you are trying to invoke
ansi-term, is that right? And the shell is just what Emacs asks you
about a program to run in the terminal? In that case, the error you
see is because ansi-term cannot work on Windows, as it needs a Unix
terminal driver and programs such as stty to support that.
Sorry I didn't spot that before: I was reading the body of your mail,
but missed the Subject line.
