re: rough new toy: mh-flists

When someone asked me where to find the emacs 21 betas, I realized
that the code still relied on emacs-21.  This version should work
around that problem.

If you're interested in becoming an emacs pretester (note: these are
not betas; they're pretest versions.  In the `modern' world of
software release practices, there's a difference), let me know and
I'll hunt down the current contact.

chad

; extension to mh-e for an active list of folders based on flists.
; $Header: /local/home/yandros/elisp/RCS/mh-flists.el,v 1.2 2001/02/02 01:59:05 yandros Exp $

(provide 'mh-flists)
(require 'mh-e)

(defvar mh-flists-mode-map (make-sparse-keymap) "Keymap for mh-flists-mode")

(defvar mh-flists-quiet nil)           ;list just folders with unread msgs?

(defvar mh-flists-buffer "mh-flists")  ;name of buffer for mh-flists

(defun mh-flists ()
  "List mail folder sizes and number of unseen messages.  Confused by
folder names that end in `+'"
  (interactive)
  (mh-find-path) ; init mh-e
  (save-excursion

Fix for BSD/OS and nmh

We've finally updated BSD/OS to nmh for the next release.  I've found
one problem.  The code in mh-find-path needs this change to be able to
find our /usr/contrib/mh/etc directory:

--- mh-utils.el-old	Thu Mar  1 21:00:07 2001
+++ mh-utils.el-new	Thu Mar  1 20:59:13 2001
 <at>  <at>  -630,7 +630,7  <at>  <at> 
 		  ;; components, then look for lib/mh or mh/lib.
 		  (or (mh-path-search
 		       (mapcar (lambda (p) (expand-file-name p mh-base))
-			       '("lib/mh" "etc/nmh" "/etc/nmh" "mh/lib" "etc"))
+			       '("lib/mh" "etc/nmh" "/etc/nmh" "mh/lib" "etc" "mh/etc"))
 		       "components"
 		       'file-exists-p))))
 	(or (and mh-lib-progs

Any objections?

What's the procedure for checking this into the CVS tree?

Thanks.

Jeff

Re: Fix for BSD/OS and nmh

Jeffrey C Honig <jch <at> honig.net> writes:
> Any objections?

  Nope. Would you like me to ask the Emacs folks if this is cool for
  Emacs 21.1, or can it wait until 21.2? Since we're so close to
  release they are leery about any source changes that aren't bug
  fixes, no matter how small.

  Hopefully by 21.2 we can generate a new mh-e release and roll the
  changes into Emacs.

> What's the procedure for checking this into the CVS tree?

  See CVS Repository
  (http://mh-e.sourceforge.net/doc/devguide.html#SEC40). I've made a
  few changes since 1.0 to this document (see the htdocs ChangeLog
  excerpt below), so I'd suggest giving it another detailed read.

  If my prose isn't brilliantly clear , please let me know and I'll
  clarify.

  I note the following in copyright.list so it's cool for you to make
  changes:

    EMACS   Jeffrey C. Honig        1997-04-25
    Disclaims changes.

  Peter and Chad, I don't see entries for you. Unless you've sent in
  your papers already (they seem to be behind in updating
  copyright.list since I sent in my Emacs papers long ago and I don't