On Fri, May 01, 1998 at 08:17:29PM +0200, Hrvoje Niksic wrote:
What does this shit do in XEmacs?
Non-nil means the buffer contents are regarded as multi-byte form
of characters, not a binary code. This affects the display, file I/O,
and behaviors of various editing commands.
Setting this to nil does not do anything.
enable_multibyte_characters = 1;
If it is for "compatibility" with broken FSFmacs mule code, then
either the code should be fixed, or it should be moved to
This *MUST* die. This tries to break the internal/lisp-visible coding
We can find traces of this junk in the tm, skk, ispell, reftex and
mule-base packages at least. They should be bobbited out.
There is also:
which show how much we care about that thing.
The variable itself isn't used in the X source, only defined in
file-coding.c and mule-coding.c.