Possible bug in create-compatibility-dot-emacs!

Michael, I just noticed something -- create-compatibility-dot-emacs always sets the init-file and custom-file to the .el versions, not the .elc ones even if they exist. Is this intentional? I also think that the code that looks for init.elc and init.el should check to make sure the .elc file is up-to-date. If not, it should load the .el file instead and issue a prominent warning about the situation. Otherwise, many people will doubtlessly get bitten by changing their .el file, forgetting to recompile, and wondering why nothing is happening! Same would go for custom.el except that presumably custom.elc is ignored, right? [If so, and if custom.elc is present, a warning should be issued about this.] Finally, if you have compiled init.el, user-init-file will currently be set to ~/.xemacs/init.elc. I think this is a definite mistake -- lots of code will undoubtedly assume that it can edit user-init-file, not realizing that the `c' has to be chopped off. e.g. the current code in menubar-items: ["Edit I%_nit File" ;; #### there should be something that holds the name that the init ;; file should be created as, when it's not present. (progn (find-file (or user-init-file "~/.xemacs/init.el")) (or (eq major-mode 'emacs-lisp-mode) (emacs-lisp-mode)))] i also think we need another variable, as this comment indicates. -- ben I'm sometimes slow in getting around to reading my mail, so if you want to reach me faster, call 520-661-6661. See http://www.666.com/ben/chronic-pain/ for the hell I've been through.