Re: A fundamental problem with defcustoms that are lists

[Stefan Monnier]

> Thanks, that is a nice idea. I think it would be good, but not
> necessary. Maybe some intermediate thing, something that reminded of
> "merge conflicts" could be used instead?

That's a very good point.  I think Custom should always store not just
the value you set, but also the corresponding original value.
Some variables often change, so we may not want to warn the user for
each and every change to every variable, but most variables's default
value never changes, so it would make sense to warn users when the
default has changed, even if that variable only holds some symbol or
number rather than a list.


        Stefan