Re: Decoding coding system of processes

[Stefan Monnier]

> I have started "emacs -q -no-site-file". Then I've performed "M-x shell" 
> and "M-: (process-coding-system (get-buffer-process (current-buffer)))"
> afterwards in the shell buffer. Surprisingly, the result is
> "(iso-latin-1-dos . iso-latin-1)".

AFAIK the reason is that as long as the output is "plain text", this correctly
handles single LF as well as CRLF line ends, which is neat since some shells
in some circumstances supposedly output CRLF, even under Unix (because they
think they're driving a terminal).

> The setting of a dos decoding system is nasty. For example, it
> instructs to Tramp convert eol characters of transferred files, as
> reported recently in emacs-pretest-bug. Where does it come from? Is it
> really the correct coding system one has to expect?

I thought Tramp converted the file's content to base64, thus making the
transfer immune to minor text rewrites such as CRLF conversion or
TAB/SPC modifications.


        Stefan