Re: Customize may not be appropriate for older users

[Francesco Potorti`]

Unfortunately, the suggestion which was the intended topic of my mail
got lost in the discussione that I involuntarily prompted with my
example file name.  

Let me try again with a less controversial example file name.

rms wrote (about customize writing in .emacs):

   I don't think these changes are needed, and they could be 
   inconvenient or troublesome.  It is better not to do them.
   
and I answered:

   I have another idea, which may be better.
   
   Currently, I have this in my .emacs, just at the beginning:
   
     (load "/etc/emacs/default" nil t)
     (setq inhibit-default-init t)
   
   That is, I exploit the excellent feature that allows me to either
   load default.el at the beginning in order to override it, or else let
   it be loaded at the end, which is the default.
   
   I think that the same criterion could be used for the code generated
   by customize: let it go in a ~/.emacs.custom.el file, and let it be
   loaded just after ~/.emacs, but with the option of preventing its
   loading by setting the variable inhibit-custom-init.
   
   This scheme would be consistent with the one already used for
   default.el, and would have the advantage of not mixing hand-made and
   automatically generated code in the same file[1].
   
   [1] In my opinion, any program which edits a hand-made file does A
       Bad Thing.