Re: Latin1 language environment breaks Cygwin shell buffer

[Eli Zaretskii <eliz@is.elta.co.il>]

[Please keep the mailing list on the CC.]

On 30 Mar 2002, Eric Hanchrow wrote:

> 
>     > (setq shell-file-name		"c:/cygwin/bin/bash")
>     > (setq explicit-shell-file-name	"c:/cygwin/bin/bash")
> 
>     ... Actually, I don't recommend setting these variables at all in
>     Emacs, but instead set up PATH and SHELL variables _outside_ Emacs
>     so that the right shell is found.
> 
> I wanted to do that, since it seems cleaner than setting Emacs
> variables, but the `runemacs' program appears to unconditionally set
> the SHELL variable to cmdproxy.exe.  (And I prefer `runemacs' to plain
> `emacs' since the former doesn't open a console window, which is
> annoying.)

AFAIK, `emacs' does not open a console window for quite some time.  When 
did you last try that, and how did you invoke Emacs when you did?

>     Also, what about your settings of process-coding-system?  What is
>     it in both language environments you used
> 
> Well, I didn't set it explicitly, as you can see, and I don't know how
> to find out what coding system is in effect.  Can you tell me which
> command to type to find out?

I believe the doc string of the `shell' command explains this.

>     does it help to use set-buffer-process-coding-system in the shell
>     buffer so that Emacs decodes Bash output with undecided-dos?
> 
> No, that doesn't help.

Then it's probably not something related to CR characters.

>     You might wish to experiment with mounting your filesystems in binary
>     (instead of text) mode.
> 
> I'm afraid they already are mounted in binary mode.

Then how come `od' shows \r characters in the output of `echo'?  
Something strange is going on here, and you probably need a Cygwin guru 
to help you out.  I suggest to ask on the Cygwin mailing list.