Re: [PATCH] Unicode Lisp reader escapes

[Richard Stallman <rms@gnu.org>]

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

    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.

We seem to be talking about two variables here:
unify-8859-on-decoding-mode and utf-fragment-on-decoding.  Are there
any others involved?

I do not know what those variables mean.  Do they affect the
choice of coding system?  Or do they take effect by altering
the meaning of a given coding system?

If it is the former, the Lisp source file can defend against this
problem by specifying coding in the -*- line.  We tell people to do this
in Lisp source files.

If it is the latter, there are two possible solutions:
1. to make the compiler bind these variables to their default values.
2. to tell people that all Lisp files for which this is relevant
   should specify these variables explicitly.

If it is just those two variables, I think #1 is easy and preferable.

Are there any other variables for which this arises?