Clarify hook pattern vs regexp in muttrc.man page.

Updates to the muttrc.man page were inadvertently not included in
changeset:aac979f8b529.  Fix mbox-hook and crypt-hook to show
they accept a regexp, not a pattern.

diff --git a/doc/muttrc.man.head b/doc/muttrc.man.head
index 30d113f17f6c035fe78e022d583e3fa50de67d75..f213734f3b13a8a54632cc896093bbbb93927a73 100644 (file)
--- a/doc/muttrc.man.head
+++ b/doc/muttrc.man.head
@@ -281,8 +281,8 @@ and subscribed mailing lists.  The \fBunsubscribe\fP command removes
 it from the list of subscribed mailing lists. The \fB-group\fP flag
 adds all of the subsequent regular expressions to the named group.
 .TP
-\fBmbox-hook\fP [\fB!\fP]\fIpattern\fP \fImailbox\fP
-When mutt changes to a mail folder which matches \fIpattern\fP,
+\fBmbox-hook\fP [\fB!\fP]\fIregexp\fP \fImailbox\fP
+When mutt changes to a mail folder which matches \fIregexp\fP,
 \fImailbox\fP will be used as the \(lqmbox\(rq folder, i.e., read
 messages will be moved to that folder when the mail folder is left.
 .IP
@@ -348,7 +348,7 @@ in the order in which they occur in the configuration file, but all
 \fBreply-hook\fPs are matched and executed before \fBsend-hook\fPs,
 regardless of their order in the configuration file.
 .TP
-\fBcrypt-hook\fP \fIpattern\fP \fIkey-id\fP
+\fBcrypt-hook\fP \fIregexp\fP \fIkey-id\fP
 The crypt-hook command provides a method by which you can
 specify the ID of the public key to be used when encrypting messages
 to a certain recipient.  The meaning of "key ID" is to be taken