Re: customize-mark-as-set for M-x foo-mode

[Richard Stallman <rms@gnu.org>]

    > For one thing, there are only a few modes you can control with the
    > menu bar, but there are dozens, maybe hundreds, you can control
    > with commands.  Should all of them update your .emacs file?
    > Maybe they should, but that is a lot of change.

    AFAIK customize-mark-as-set does not itself update the .emacs file.
    It just marks the variable as "changed by customize" rather
    than "changed by some external thingy".  It might indeed cause the
    variable to be saved later on if you custom-save-all.  I don't know
    how important that is.

Please excuse my inadequate memory.  I see no possible harm in marking
the variable as changed.  So the question is simply whether we should try
to change as many minor modes as possible, or only some of them, or none.

If we succeed in changing most minor modes this way, but a few
(perhaps user-implemented) remain unchanged, will the inconsistency be
confusing, or will that be better than nothing?