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

[Kenichi Handa]

In article <address@hidden>, Eli Zaretskii <address@hidden> writes:

> So, given your explanation about the nil value of
> buffer-file-coding-system, do you agree that we need to change
> mule-cmds.el so that reset-language-environment sets the default
> buffer-file-coding-system to dos on MS-DOS and MS-Windows?  Or are you
> saying that with your change in coding.c, the issue of creating new
> files is already taken care of, and no further changes are required?

Yes, I think there's no need for further changes.

>> If buffer-file-coding-system is dos, and some other file is
>> inserted with decoding, the buffer-file-coding-system is
>> changed to XXX-dos where, XXX part is the text-encoding part
>> of the coding-system used for that decoding.

> Do we want it to change to XXX-dos on Windows,

What do you mean by "it" above?

> or do we want the inserted file to determine EOL
> conversion as well?

Yes, because it's the behavior on Unix/GNU-Linux.

> I tend to think that we want XXX-dos regardless of the
> inserted file.

With my change, even if the inserted file has no newline,
and thus EOL part of the buffer-file-coding-system is still
not decided, when a user input a newline in that buffer, it
is encoded into CRLF.  Isn't it not enough?

---
Kenichi Handa
address@hidden