Re: "Attempt to modify read-only object" error with set-frame-configuration

[martin rudalics]

> I think this means that your previous patch and the one you suggest
> here is not the correct solution.  We must first understand what is
> the problem with initial frame parameters on w32, and what causes that
> problem.

I think something like this patch is needed to avoid that the fringes
creep into `initial-frame-alist' and `default-frame-alist'.  Otherwise,
customizing these is broken.  And the fringes show up multiple times in
`frame-parameters' due to the simple-minded

              (setq frame-initial-frame-alist
                    (append initial-frame-alist default-frame-alist nil))

in `frame-initialize'.