Re: [PATCH] Unicode Lisp reader escapes

[Kenichi Handa <handa@m17n.org>]

In article <87irohfrx1.fsf@gmx.de>, Oliver Scholz <alkibiades@gmx.de> writes:

>> (progn
>> (let ((str "(setq x \"\300\300\")\n")
>> (coding-system-for-write 'no-conversion))
>> (write-region str nil "~/test1.el")
>> (write-region str nil "~/test2.el"))
>> (set-language-environment "Latin-1")
>> (byte-compile-file "~/test1.el")
>> (set-language-environment "Japanese")
>> (byte-compile-file "~/test2.el"))

> That's not exactly what I meant. This happens basically because Emacs
> has no indication on how to decode that file properly. Here's a test
> case for what I had in mind:

The underlining problem is the same.  In your test case
also, even if you put coding: tags, the exact decoding
varies depending on many other things, and thus resulting
*.elc are different.

[...]
> As Richard wrote, the fix would be to change the settings to
> their default, unless the files set a specific variable.

Then you'll get different results in these two cases:

(1) visit *.el and M-x eval-current-buffer
(2) byte-compile *.el and load *.elc.

I think that is more like a bug.

> But given the work this would require and given that the value of
> changing the defaults is IMO somewhat dubious, you could as well
> just document it in etc/PROBLEMS.

I agree that is the best solution.

---
Kenichi Handa
handa@m17n.org