Re: [PATCH] Unicode Lisp reader escapes

[Richard Stallman]

    > Here's one idea: if the -*- line specifies `coding' and specifies
    > the mode `emacs-lisp' then force unify-8859-on-decoding to nil
    > for that file.

    Forcing it to nil for a particular file is maybe too much work to implement
    compared to th benefit.

What makes it hard?

    Maybe an easier solution is to add a file-local variable
    `no-8859-unification' such that if that file is loaded in an Emacs which
    is configured to use unify-8859-on-decoding it signals an error.

Why is it much harder to switch to the nil mode
than to signal an error?