Re: customize-mark-as-set for M-x foo-mode

[Per Abrahamsen <abraham@dina.kvl.dk>]

"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:

>>     Is there any reason why it's only executed when run from the
>>     menu-bar rather than from M-x ?

I think it would be a significant improvement to make M-x mark them as
customized rather than rogue.

The only purpose by distinguishing betten "set by customize" and "set
outside customize" is to warn the user that saving the variable from
customize may have no effect, because "something else" (like an
explicit setq in .emacs) will be overwriting the saved value next time
he start Emacs.

If "something else" is an explicit, interactive command by the user,
there is no reason to warn him.

> AFAIK customize-mark-as-set does not itself update the .emacs file.

True.

> It might indeed cause the variable to be saved later on if you
> custom-save-all.

Nope.  Only those marked for saving will be saved.

However, it will make the variable appear in the list generated by
customize-customized, which I would consider an extra bonus.

>> Maybe it would be better if none of these commands updated .emacs
>> itself, and instead there were another command in the Options menu to
>> save the options that you can (or that you have) set with the Options
>> menu.
>
> I don't understand.  It's already the current behavior AFAIU.

Yes, that is the current behavior.  "Options -> Save Options" saves
all options that you _can_ set from the options menu with their
current value, no matter how you have actually set them.