Re: XEmacs 21.4.5 "Civil Service" is released.

From: Stephen J. Turnbull <stephen(a)xemacs.org&gt; Date: 24 Oct 2001 09:50:24 +0900 Putting it into sample.init.el would be a good idea, though (how about a patch?) You know, the sample.init.el is at the same time, both way too much and not nearly enough. The sample.init.el file is way too complicated for a novice type person who just wants to add some keybindings, or load some packages. On the other hand, there are no examples of face customizations. There are some good ideas is the sample file, but all those defuns are scary. I would suggest that we have a simple init file that goes into a certain level of detail, does some requires and global-set-keys, maybe a few useful options. Then I would suggest that we split the sample.init.el file into several sample files, with each file being more topic oriented. And then have a not so simple init file that is split up into several files. For example, our main init file is something like: ;; Standard Packages that we want all the time. (require 'vc-hooks) (require 'font-lock) (require 'paren) (if (null paren-mode) (paren-set-mode 'paren)) (require 'redo) (setq-default uniquify-buffer-name-style 'post-forward-angle-brackets) ;; forward, reverse, (require 'uniquify) (icomplete-mode) ;; preference files split up by topic. (require 'new-features) ;; nifty new functions (require 'xemacs-patches) ;; bug fix patches and improvements (require 'font-preferences) ;; face customizations (require 'general-preferences) ;; global settings and bindings (require 'mode-preferences) ;; option settings for various modes (require 'mailer-preferences) ;; settings for vm, gnus, mailcrypt, I have the init files under cvs and shared on different machines (windows & unix) with multiple xemacs releases. Up till now my .emacs file has always been a complete mess. So far, the only real problems in switching from one xemacs release to another has been in the face customizations. BTW, The sample.init.el has various grep commands - like 'grep-all-files-in-current-directory'. Is there a reason why the igrep package is not being used? Maybe igrep doesn't do the recursive grep command? -jeff