Changing the MH Environment

As the Section Settings from the Environment explains, some MH commands add environment variables that are passed to environments of their child processes. MH commands also read their own environments, set by their parent processes. For example, if the variable MHCONTEXT is set, MH commands will use that pathname for the MH context file instead of the file named context in the MH directory.

The Table below was adapted from the mh-profile(5) manual page. For more description of each environment variable, see that manual page. This table doesn't include environment variables used by parts of MH (like BBoards) which this book doesn't cover.

Table: Environment Variables that MH Checks

HOME (checked by all commands)

Full pathname of your home directory.

MAILDROP (checked by inc)

Default maildrop (like /usr/spool/mail/ehuser).

MH (checked by all commands)

Pathname of MH profile (default: .mh_profile in home directory). (See NOTE after table.)

MHCONTEXT (checked by all commands)

Pathname of context file.

NOMHNPROC (checked by show, next, prev)

Don't run the mhnproc (usually mhn or mhshow) for MIME messages. (Obsolete in nmh; use the -nocheckmime command line switch instead.)

SIGNATURE (checked by send, post)

Your name, for From: field (for example, "Emma H. User").

TERM, TERMCAP (checked by scan, mhl)

Terminal information; see the environ(5) manual page.

NOTE: xmh Release 4, and possibly earlier versions too, ignore the MH environment variable at startup time. It always reads the .mh_profile in your home directory to find the Path: of your MH directory. There's a workaround in Section Conflicts Between xmh and MH Customization.