> From: Ralf Angeli <[EMAIL PROTECTED]> > Date: Mon, 10 Apr 2006 23:07:00 +0200 > > > However, the behavior of Emacs on non-Posix platforms under LANG=C > > raises a subtle issue. Right now, when LANG=C (or Posix), > > set-locale-environment sets up things so that the default > > buffer-file-coding-system is reset to nil, and that causes Emacs to > > create files with Unix-style EOL conversion. This happens because the > > "C" language is mapped to "ASCII", which specifies no encoding. Thus, > > set-language-environment resets the default coding systems to nil, and > > leaves it at that. Then the code which takes care of copying the EOL > > conversion from previous defaults doesn't do its thing. > > > > The question is, is this a bug or a feature? That is, is it right for > > Emacs on MS-Windows to create Unix-style text files under LANG=C? I > > tend to think it's a bug, but I'm not sure. > > Isn't that an academic question? Are there people running Emacs > intentionally under LANG=C and expecting Windows-style line endings?
I don't think it's academic: you yourself found one example of running Emacs under LANG=C, albeit non-interactively. Suppose Emacs needed to create a file during that non-interactive session---is it okay for that file to be in Unix text format? I know that I'd be surprised to learn about such behavior. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
