Re: customize - convenience group changes frame fringe setting

[Richard Stallman]

    Why would one way of changing default-frame-alist be any different from
    another? I would think that the last change would rule, however it was
    effected.

The problem is that the option fringe-mode is a variable and has a value.
If you set default-frame-alist to specify no fringes, the value of
fringe-mode becomes unrelated to the facts in default-frame-alist that
normally it would control.

By the way, I remembered why I changed the default for :initialize to
custom-initialize-reset.  It is for the sake of autoloaded customize
options, whose values were first initialized by loaddefs.el.  However,
the defcustom isn't loaded until later.  So if there is something
nontrivial to do for initialization, it needs to be done later.
And this takes care of possible setq's done by the user in the
mean time.

Possibly custom-initialize-reset is the wrong thing to use
for fringe-mode.