Re: Wrong type argument: arrayp, nil with LANG=C under Windows

[Ralf Angeli]

* Eli Zaretskii (2006-04-10) writes:

>> From: Ralf Angeli <address@hidden>
>> 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.

Thanks, I'll do this as soon as I will have access to a better
connection again.  (Or find out why cvs sends half of the repository
to the server during an update.)

> 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?

-- 
Ralf