Re: address@hidden: setting utf-16 as file-name-coding-system locks up emacs]

[Kenichi Handa]

In article <address@hidden>, Richard Stallman <address@hidden> writes:

> Can you please work on this?
> ------- Start of forwarded message -------
> Date: Fri, 6 Aug 2004 15:04:39 +0200
> From: Mattis <address@hidden>
> To: address@hidden
> Subject: setting utf-16 as file-name-coding-system locks up emacs
[...]
> This is what I do to get this error:

> 1. Start emacs using --no-init-file
> 2. M-: (setq debug-on-quit t)
> 3. C-g -- to make emacs load debug, which it will not be
>           able to load after I change the
>           file-name-coding-system
> 4. (setq file-name-coding-system 'utf-16)
> 5. Wait for a while
> 6. After switching back to emacs seems to have frozen
> 7. "Unfreeze" with C-g

> This is what I get:

>   Debugger entered--Lisp error: (quit)
>     utf-8-pre-write-conversion(1 4)
>     file-exists-p("h:/")
>     make-directory("h:/.emacs.d/auto-save-list/" t)

> The error is not all the one above, even though the
> make-directory part seems to be there most of the times.

As you set file-name-coding-system to utf-16, emacs is going
to make an auto-saving file in a directory
"h:/.emacs.d/auto-save-list/" encoded in utf-16.  I don't
know if it's possible on Windows to make such a directory,
but I believe that it's not what you want.

Why do you have to set file-name-coding-system to utf-16?

In geneneral, setting file-name-coding-system to something
other than locale-coding-system (cp1252 in your case) leads
to bad result unless you know exactly what you are doing.
For instance, other applications can't recognize such a file
name.

---
Ken'ichi HANDA
address@hidden