RE: customize - convenience group changes frame fringe setting

[Drew Adams]

When you say "we" change default-frame-alist - do you mean that it is
changed by program? That doesn't sound like a good idea. I would expect
default-frame-alist to be under user control, and not be changed behind the
user's back. He defines frames the way he wants using this variable; why
would we change it? Perhaps I misunderstand what you mean.

If I understand right, you said that clicking the Convenience group loads
fringe.el, which executes a defcustom for fringe-mode, which calls
set-fringe-mode-1. That means that clicking a _navigational_ button in
customize has the side effect of changing the default-frame-alist. Not good
(if I understand right).


-----Original Message-----From: Richard Stallman [mailto:address@hidden

    Not sure if your question was to me. I don't know how it _does_ behave,
but
    I would guess how it _should_ behave:

     - Explicit settings of any frame parameters should override existing
frame
    parameter values for that frame.

     - The default values shouldn't change, however, so new frames should
still
    reflect the default.

In this case it is a conflict between two defaults.  We change
default-frame-alist, which specifies the settings for all new frames.
So the effect of fringe-mode would be completely overridden.