Re: Customize key bindings?

[Simon Josefsson]

Luc Teirlinck <address@hidden> writes:

> Simon Josefsson wrote:
>
>    Looking into why the :set functions need to do set-default for
>    customize-variable to pick up the currently set valued would be useful
>    as well.  (See comment about custom bug below.)
>
> Why is this a bug?  Custom sets default values, so it has to use
> set-default.  (What else would you have wanted to use?)

It might not be a bug, but without set-default you get a rather
surprising result:

start emacs
M-x customize-variable RET custom-key-alist RET
add some settings
click on set + save
quit emacs

<<the variable the user selected is stored in .emacs>>
<<the variable itself in the running emacs was still nil>>

start emacs
M-x customize-variable RET custom-key-alist RET
the list is now empty?
clicking on set + save loses the settings made previously?

I think I understand why it behave like this now -- customize only
customizes real variable values, and the :set should be responsible
for setting the variable as well.  I removed the comment about a
custom bug in my second release of custom-key.el to gnu.emacs.sources,
after realizing this, last night.

(Perhaps the "save" step in part 1 above really shouldn't have stored
the values the user selected?  It should have saved the contents of
the variable, the value after calling :set?)