Re: Starnge comment in Custom Theme code.

["Richard M. Stallman" <rms@gnu.org>]

    I believe that setq expresses just as much an individual preference by
    the user than a saving or setting through Custom.

That is true in some cases, but it is hard to say anything general
about why a variable was setq'd.

						       If a program did
    the setq, the situation may be worse, because the program may be
    relying on the setq-ed value for its proper functioning.

That is true in some cases.

    If the user sets cua-mode via Custom then cua-mode seems to set
    transient-mark-mode, delete-selection-mode and pc-selection-mode using
    setq or minor mode invocation.

That is an unclean way to do things--I am not surprised that it can
lead to problems.  I can imagine other scenarios where Custom, not
using themes, would give perplexing results for these variables.

I don't know what we should do about it.  Perhaps nothing; it may not
be worth the effort to solve this "right".  However, I don't think we
should try to draw any conclusions about custom themes from a case as
screwed-up as this one.