Re: Customize Rogue

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

Juanma Barranquero <lektu@terra.es> writes:

> I reacted to the word "transition"**, 

Does the word have any special positive or negative connotations?

>  1.- Not getting the "modified outside of customize" messages that I get
> the odd time I use it. 

They are there for a reason.

> If the value is right, I don't see the point of
> knowing i.e. if I set custom-file to ".emacs.custom" via setq or through
> M-x customize-variable; the message makes me wonder if anything's wrong...

Which is good, because if you have set it with setq and you try to
save it with customize, the customize save will be overwritten by the
setq.

custom-file probably should not have been declared with defcustom, as
it make no sense to change it throug customize.

>  2.- Using the customized initialization/setting/getting/whatever code
> for those variables that have special needs. I'd like to do
>
>   (custom-setq variable value)   ; or whatever
>
> and get customize to check the value against the type spec, etc.

customize-set-value only make type-checks when used interactively,
when used from Lisp is works just like setq.

customize-set-variable will tell customize the variable has been set
interactively, and call any speciel ":set" functions.

The first property means it should never be called from ".emacs", but
the second could be generally useful.  

Maybe we should have a function that does the second (obey :set)
without doing the first.  I'm not a Common Lisp programmer, but I
suspect it would be natural to use setf for that purpose.  This way we
could do things like

  (setf menu-bar-mode nil)

and it would just work.