Re: Changed outside --> set, in Customize UI

[Stefan Monnier <monnier@iro.umontreal.ca>]

> One problem mentioned is that trying to save a "changed-outside"
> option might not "work": some library you load might change the saved
> value to something different after you restart. Well, _setting_ an
> option in Customize and then saving it might not work either - for
> exactly the same reason. If users think they can rely on _not_ seeing
> a changed-outside "warning", then they are misled. If you see a
> changed-outside warning, beware; if you don't see such a warning,
> beware. This is a distinction without a distinction.

Nice theory, but in practice there is a big difference, because in most
cases the "changes outside customize" either always take place or never take
place, so it's a rare occurrence when the problem you mention shows up.

And even if it does show up, taking a look at the customize buffer when you
see the problem will tell you "changed outside customize" warning you of
the problem.

What is the problem you are trying to solve, really?
I.e. in what way is the message "changed outside customize" a problem?


        Stefan