Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!ucbvax!hplabs!hpfcso!hpfcdj!jayavant From: jayavant@hpfcdj.HP.COM (Rajeev Jayavant) Newsgroups: comp.emacs Subject: Re: mh-e Message-ID: <16940001@hpfcdj.HP.COM> Date: 13 Aug 90 19:14:17 GMT References: Organization: Hewlett Packard -- Fort Collins, CO Lines: 29 / hpfcdj:comp.emacs / kpc00@JUTS.ccc.amdahl.com (kpc) / 9:35 pm Aug 9, 1990 / >> Can anybody describe some of the relative advantages and disadvantages >> of mh-e wrt rmail? (mh-e is an mh front end. It appears that you >> must have mh to use mh-e. Will this be true in v19?) I have used both in the past. Initially I used mh-e because I was already using mh outside of emacs and wanted to be able to access my existing mail messages. When I migrated to a machine that didn't have mh installed, I switched to rmail. The two interfaces are pretty similar, though a couple of notable differences are mentioned below. rmail has the advantage of consolidating all of the messages in a "folder" into a single file. mh creates a separate directory for each folder with a separate file for each message. While rmail tended to keep my directories cleaner, I liked the way header information is managed in the mh-e mode much better, and I have gone back to using mh-e. Unless rmail has been updated, it only had an option to generate a list of message headers which you couldn't really mainpulate. In mh-e, there is a 3 line window containing only headers which you can browse through. Keystrokes can be used in the header window to view, delete, answer,etc. the message corresponding to the selected header. Rajeev ------------------------------------------------------------------------------ Rajeev Jayavant (rajeev@hpfcla.hp.com) "Excuse me, I've lost my marbles" Hewlett Packard - Graphics Technology Division - P. Opus, [Bloom County]