Re: customize-rouge output with emacs -q --no-site-file

[Luc Teirlinck <teirllm@dms.auburn.edu>]

>From my earlier message:

   If we now make changes to Emacs that require adding other
   elements to these hooks, lists or alists, or removing elements, the
   user does not get those values, because he hardwired the old value in
   his .emacs.

Actually, thinking about it, this particular problem can occur when
customizing _any_ hook, list or alist through Custom.  Basically,
whenever you are not supposed to just setq an option, setting it
through Custom is dangerous, because you _are_ setq-ing it.  For
instance, I have before-save-hook set through Custom.  This is
currently not a rogue variable, no problem.  But whenever somebody
would, say fix a bug or implement a new feature by adding a function
to before-save-hook, my Emacs will not see it.  My .emacs will
override it.  In other words, before-save-hook is not rogue now, but
anytime that I update my CVS, it could become rogue.  Personally, I
will get rid of this entry in custom-set-variables and use add-hook in
my .emacs.  Much safer.

Sincerely,

Luc.