>>>> "Hilko" == Hilko Bengen
<bengen(a)hilluzination.de> writes:
> (require 'un-define)
> (set-variable 'coding-system-for-read 'utf-8)
> (set-variable 'coding-system-for-write 'utf-8)
> (require 'crypt)
Hilko> It looks to me as if the files' content were mangled by the
Hilko> coding-system mechanisms before and after feeding it to the
Hilko> external programs.
That's what you asked for; you got it. Don't `set' those variables;
that is documented as inappropriate usage. Use
buffer-file-coding-system and friends, instead.
The freeze is surely a bug, but since Mule-UCS is a stopgap
unsupported orphaned library written in an arcane little language
targeted at an even more arcane byte-code engine (ie, not the regular
Lisp engine), it's highly unlikely that anyone will work on it. If
you really need to do this kind of thing, use 21.5.
It's possible that this particular case could be avoided by having
crypt bind those variables itself, but it's not immediately obvious
that it is the right thing to do even for crypt (since crypt is a
generic mechanism for various such purposes, some of which might be
text-based for all we know), and there are other cases where the Lisp
library explicitly wants to allow overrides, so it cannot use those
variables itself. In those cases you will get data corruption.
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.