|
|
1.1 root 1: .TH MHE
2: .SH NAME
3: mhe \- Display interface to Rand Mail Handler
4: .SH DESCRIPTION
5: .I MHE
6: is a program that provides an Emacs-based display-oriented front end to the
7: Rand Mail Handler. By Emacs-based we mean that it is actually implemented as
8: an extensive macro package in Emacs, thereby providing access to full Emacs
9: at all points. By display-oriented, we mean that it provides windows on mail
10: messages and headers so that you can edit your mail directory as if it were
11: a file.
12: .PP
13: To get started using \fIMHE\fR without being an expert at \fIMH\fR, just
14: type ``mhe'' to the shell. It will start up Emacs, load the macro package,
15: tell you how to initialize things if you have not already done so, and then
16: (assuming things are initialized properly) load your inbox headers into its
17: current window in a buffer named ``+inbox''. You can then type various
18: 1-character commands to do mail operations. The ``?'' command asks for help.
19: .PP
20: If you want to use the Emacs that is inside \fIMHE\fR, just visit a file
21: with C-X C-V, in the normal way. If you want to return to the \fIMHE\fR
22: code, just make the buffer ``+inbox'' visible again; the key bindings are
23: buffer-local, and will magically return to their mail-reading meanings.
24: .SH SEE ALSO
25: .nf
26: .ta 1.5i
27: mh (1) - the Rand Mail Handler
28: .SH AUTHOR
29: Brian K. Reid
30: .SH BUGS
31: There is a fundamental design bug in the Unix kernel that prevents more than
32: one Emacs process from being able to run at a time. \fIMHE\fR is implemented
33: in Emacs. This means that you cannot have a mail-reading job and an editing
34: job active simultaneously. However, since you have access to all of Emacs
35: while inside \fIMHE\fR, this is not a serious problem.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.