Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!ig!jade!ucbvax!homer.Berkeley.EDU!larus
From: larus@homer.Berkeley.EDU.berkeley.edu (James Larus)
Newsgroups: comp.emacs
Subject: Re: Using mh from emacs
Message-ID: <21689@ucbvax.BERKELEY.EDU>
Date: Mon, 9-Nov-87 13:06:13 EST
Article-I.D.: ucbvax.21689
Posted: Mon Nov  9 13:06:13 1987
Date-Received: Wed, 11-Nov-87 06:25:18 EST
References: <830002@hpcilzb.HP.COM> <437@ucdavis.ucdavis.edu> <5319@ncoast.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: larus@homer.Berkeley.EDU.UUCP (James Larus)
Organization: University of California, Berkeley
Lines: 26


>I have a question about mh-e, by the way:  I can't see a way to get out of
>it without doing a switch-to-buffer (C-xb) and naming the buffer; I have
>kluged around this for now by having C-xr call a function which saves the
>current buffer in a variable and calling mh-rmail, then setting up an
>mh-folder-mode-hook which binds 'q' to a function which restores the original
>buffer after doing a (bury-buffer (current-buffer)).  But this leaves
>(other-buffer) as "scan-+inbox"; I could (bury-buffer (other-buffer)) as well,
>but what if there are other mh-rmail buffers as well?  (Please don't tell me
>to RTFM; no manual as yet, I'll have to order one.)
>-- 
>Brandon S. Allbery		     necntc!ncoast!allbery@harvard.harvard.edu
> {harvard!necntc,well!hoptoad,sun!mandrill!hal,uunet!hnsurg3}!ncoast!allbery
>			Moderator of comp.sources.misc

You are correct, you can't get out of mh-e (chuckle, chuckle).  It is designed
like other environments in GNU emacs: the commands are associated with a buffer
and you "quit" by killing the buffer or changing buffers.  mh-e is a bit more
complicated since it generally has more than one buffer (e.g., show-+inbox).
The latest and greatest version of mh-e ameilorates this problem by burying
these buffers.  Hence, you can read your mail and then go back to what you
were doing by ^X-b.

/Jim
ucbvax!larus
larus@ginger.Berkeley.EDU