comp - compose an nmh message
| Use Case | Command | Description |
|---|---|---|
| Compose a new message | comp |
π Creates a new draft from the default template. |
| Continue editing an existing draft | comp -use |
π Resumes composition of a previously unsent draft. |
| Use a custom form file | comp -form formfile |
π Uses a specified template (see mh-format(5)). |
| Use an existing message as a base | comp +folder or comp msg |
π¬ Copies an existing message into the draft. |
| Use a file as the draft | comp -file file |
π Loads the specified file as the draft. |
| Specify sender address | comp -from address |
π§ Sets the From: field. |
| Specify recipient(s) | comp -to address |
π₯ Adds addresses to the To: field. |
| Specify CC recipients | comp -cc address |
π¨ Adds addresses to the Cc: field. |
| Set subject | comp -subject text |
π Sets the Subject: field. |
| Set Fcc folder | comp -fcc +folder |
π Specifies the folder for saving a copy. |
| Use a different editor | comp -editor editor |
βοΈ Overrides the default editor for the initial edit. |
| Skip initial edit | comp -noedit |
π« Suppresses the initial editor invocation. |
| Build draft without sending (for mh-e) | comp -build |
π§ Creates a draft file <mh-dir>/draft and exits. |
comp [-help] [-version] [+folder] [msg] [-form formfile] [-use |
-nouse] [-file file] [-draftfolder +folder] [-draftmessage msg]
[-nodraftfolder] [-editor editor] [-noedit] [-width columns]
[-from address] [-to address] [-cc address] [-fcc +folder] [-subβ
ject text] [-whatnowproc program] [-nowhatnowproc] [-build]
comp is used to create a new message to be mailed. It copies a message form to the draft being composed and then invokes an editor on the draft (unless -noedit is given, in which case the initial edit is suppressed).
The default message template βcomponentsβ will direct comp to construct the message draft as follows:
From: {from switch} or <Local-Mailbox> or <username@hostname>
To: {to switch} or blank
cc: {cc switch} or blank
Fcc: {fcc switch} or +outbox
Subject: {subject switch} or blank
If a file named βcomponentsβ exists in the user's nmh directory, it will be used instead of this form. You may specify an alternate forms file with the switch -form formfile.
You may also start comp using the contents of an existing message as the form. If you supply either a +folder or msg argument, that message will be used as the message form. You may not supply both a -form formfile and a +folder or msg argument. The line of dashes or a blank line must be left between the header and the body of the message for the message to be identified properly when it is sent (see send(1)).
The switch -use directs comp to continue editing an already started message. That is, if a comp (or dist, repl, or forw) is terminated without sending the draft, the draft can be edited again via βcomp -useβ.
The -file file switch says to use the named file as the message draft.
Forms that are selected via the -form switch are processed via the nmh template system; see mh-format(5) for details. Drafts constructed from another message or with the -use or -file switches will not be processed with mh-format(5).
In addition to the standard mh-format(5) escapes, the following component escapes are either new or have an alternate meaning:
| Escape | Returns | Description |
|---|---|---|
| fcc | string | Any folders specified with -fcc folder |
| from | string | Any addresses specified with -from address |
| to | string | Any addresses specified with -to address |
| cc | string | Any addresses specified with -cc address |
| subject | string | Any text specified with -subject text |
By default the βTo:β and βcc:β fields are empty. You may add addresses to these fields with the -to address and -cc address switches. You may give these switches multiple times to add multiple addresses.
By default the βFrom:β field has either the value of the Local-Mailbox profile entry or a system default email address. This default can be overridden by using the -from address switch. The default mailbox in the βFcc:β field is +outbox. This can be overridden by the -fcc switch.
Any text you give to the -subject switch will be placed in the βSubject:β field in the draft.
If the draft already exists, comp will ask you as to the disposition of the draft. A reply of quit will abort comp, leaving the draft intact; replace will replace the existing draft with the appropriate form; list will display the draft; use will use the draft for further composition; and refile +folder will file the draft in the given folder, and give you a new draft with the appropriate form. (The +folder argument to refile is required.)
The -draftfolder +folder and -draftmessage msg switches invoke the nmh draft folder facility. This is an advanced (and highly useful) feature. Consult the mh-draft(5) man page for more information.
The -editor editor switch indicates the editor to use for the initial edit. Upon exiting from the editor, comp will invoke the whatnow program (see whatnow(1) for a discussion of available options). The invocation of this program can be inhibited by using the -nowhatnowproc switch. (In fact, it is the whatnow program which starts the initial edit. Hence, -nowhatnowproc will prevent any edit from occurring.)
The -build switch is intended to be used by the Emacs mh-e interface to nmh. It implies -nowhatnowproc. It causes a file <mh-dir>/draft to be created, containing the draft message that would normally be presented to the user for editing. No mail is actually sent.
/etc/nmh/components β The default message skeleton.<mh-dir>/components β The user's message skeleton.$HOME/.mh_profile β The user's profile.Path: β To determine the user's nmh directory.Draft-Folder: β To find the default draft-folder.Editor: β To override the default editor.Msg-Protect: β To set mode when creating a new message (draft).fileproc: β Program to refile the message.whatnowproc: β Program to ask the βWhat now?β questions.+folder β The current folder.msg β The current message.-nodraftfolder-nouseNone
If whatnowproc is whatnow, then comp uses a built-in whatnow, it does not actually run the whatnow program. Hence, if you define your own whatnowproc, don't call it whatnow since comp won't run it.
Generated by phpman v4.9.26-5-g7740029 Author: Che Dong Under GNU General Public License
2026-08-16 10:13 @2600:1f28:365:80b0:7cb9:fb:26c1:e368
CrawledBy CCBot/2.0 (https://commoncrawl.org/faq/)