[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: toggling a minor mode should not tell Customize that the value has b

From: Drew Adams
Subject: RE: toggling a minor mode should not tell Customize that the value has been set
Date: Sun, 6 Jan 2008 15:41:13 -0800

>  > Putting `customize-customized' on `kill-emacs-query-functions'
>  > is analogous to Emacs telling you that you have unsaved modified
>  > buffers, and asking if you want to quit anyway and lose your
>  > changes. Toggling a mode variable is not an act of customization;
>  > there is no loss if you exit without saving the latest value.
> There is.  Suppose you have done "set for current session only" and some
> action changes this to "CHANGED outside Customize; operating on it here
> may be unreliable".  When you now exit Emacs you will _not_ get warned
> that you have unsaved customizations.

Fair enough. Would you then change all commands that change option values so
that they too tell Customize that the value has been customized? Would you
somehow make sure that not only commands but all Lisp code does the same

If not, then the problem you raise remains for every option other than a
minor-mode variable. No - it remains even for a minor-mode variable, except
when it is toggled via its mode command.

What is special about toggling a minor mode in this respect? Why is it an
exception? That is the question.

Making a minor-mode toggle command do this does not take care of the general
issue you raise, in any case. And if a user is really worried about the
scenario you raise, then s?he can use `customize-rogue' instead of
`customize-customized' in the hook.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]