coding-system lossage with eterm
I installed eterm-1.04, and noticed that the CR characters are being
eaten without eterm actually doing a carriage return, resulting in the
`staircase effect'.
Using (setq process-coding-system-alist '((".*" . binary))) fixed the
problem, but it smells as if eterm is assuming that the coding system
is appropriate rather than making it so.
Is this MULE-related? Did anyone actually test eterm-1.04 on a MULE
XEmacs?
--
Glynn Clements <glynn(a)sensei.co.uk>