Re: term.el not working (Emacs21 on Win2K)

[Jason Rumney]

Does M-x shell work better for you?

I have never heard of anyone trying to use M-x term on Windows before,
so maybe it does not work. I will have a look next time I am using
Windows. I do know that many people are using `shell' successfully on
Windows.


lyongu@ailab.pku.edu.cn (Yong Lu) writes:

> In GNU Emacs 21.1.1 (i386-mingw-nt5.0.2195)
>  of 2001-10-23 on ODYSSEY
> configured using `configure --with-gcc (2.95)'
> Important settings:
>   value of $LC_ALL: nil
>   value of $LC_COLLATE: nil
>   value of $LC_CTYPE: nil
>   value of $LC_MESSAGES: nil
>   value of $LC_MONETARY: nil
>   value of $LC_NUMERIC: nil
>   value of $LC_TIME: nil
>   value of $LANG: CHS
>   locale-coding-system: chinese-iso-8bit-dos
>   default-enable-multibyte-characters: t
>   default-process-coding-system: (chinese-iso-8bit-dos . chinese-iso-8bit-dos)
>   default-keyboard-coding-system: chinese-iso-8bit-dos
> 
> Hi, there's some problem with term.el and it doesn't work with Emacs21
> on Windows 2000.
> 
> The first problem is term-exec-1 use /bin/sh to execute programs, which
> should be cmdproxy.exe in the windows port.  And it assumes the program
> 'stty' exists, which is not the case.
> 
> The second problem comes after I change the hard-coded /bin/sh to
> cmdproxy.exe.  Now I also use cmdproxy.exe as the shell, but the term
> buffer doesn't echo what I've input, and I have to use C-j to enter
> the commands.  RETURN key just doesn't work.
> 
> The third problem is I can't use the cygwin port of bash with term.  I
> suspect it's part of the NL CR conversion problem, but can't fix it by
> myself.
> 
> I also try to set process-coding-system and keyboard-coding-system to
> 'chinese-iso-8bit-unix, but it still doesn't work.
> 
> Any comments?
> 
> Yong LU

-- 
Jason Rumney