> From: Ralf Angeli <[EMAIL PROTECTED]> > Date: Sun, 09 Apr 2006 13:32:35 +0200 > > Trying to start Emacs from an MSYS shell with the command line > > LANG=C <drive>:/path/to/emacs -Q > > results in > > Wrong type argument: arrayp, nil
Thanks, I think I fixed this; please try again. 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. (For that matter, what does it mean for buffer-file-coding-system to be nil?) Any thoughts? _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
