Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!EXPO.LCS.MIT.EDU!gildea
From: gildea@EXPO.LCS.MIT.EDU (Stephen Gildea)
Newsgroups: comp.mail.mh
Subject: Re: Mh-e.el antisocial??
Message-ID: <9106211520.AA07388@alex.lcs.mit.edu>
Date: 21 Jun 91 15:20:02 GMT
References: <1991Jun13.153240.23455@uunet.uu.net>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 46


    1) If I try to start out my mh session by doing mh-visit-folder, it
    complains because the mh-temp buffer doesn't already exist. Ugly... I
    get around this by doing an mh-list-folders first, but that's a kludge.

mh-visit-folder is not an "entry point," that is, a function which
will start up mh-e properly.  Instead call mh-rmail with an argument,
which will initialize mh-e and prompt for a folder to visit.
    
    2) If mh-e hasn't visited the folder before, it cames it doesn't exist
    and asks if I want to create it. The .mh_sequences file is already there
    and the folder exists. It shouldn't really object that the folder
    doesn't exist.

This problem may be caused by incorrect entry to mh-e.  See above.
    
    3) When I do "a" to reply to a message, it complains that $MHHOME/reply
    file doesn't exist and then creates a buffer "draft-mhpath: bad message
    list drafts". If I do it again, it creates a buffer "draft-draft-..."
    and still complains about the reply file. I use a drafts folder, and I
    have mh-draft-folder set to "drafts". It does create the reply file and
    puts the message in it, but the file contents don't wind up in the
    draft-mhpath buffer. Finally, it winds up putting the results of the
    edit in $MHHOME/../"mhpath: bad message list drafts" (complete with
    spaces in the file name.

You should not be setting mh-draft-folder yourself; it gets set
automatically when the Draft-Folder line is read from your profile at
mh-e startup time.  Again, this may be caused by incorrect entry to mh-e.
    
    4) When you mark things for deletion and then quit without forces the
    updates, it doesn't ask if you might want to force the updates.

That's a feature, not a bug :-)  But you can define a new function to
do the action you want:

(define mh-update-and-quit ()
  "Execute queued folder commands and quit mh-e."
  (interactive)
  (mh-execute-commands)
  (mh-quit))



 < Stephen
   MIT X Consortium