50 |
|
|
51 |
%<{subject}Subject: Re: %(unre{subject})\\n%> |
%<{subject}Subject: Re: %(unre{subject})\\n%> |
52 |
|
|
53 |
|
*** reply_regex |
54 |
|
Argument: string |
55 |
|
Return: none |
56 |
|
|
57 |
|
Sets the regular expression used to recognize reply messages. The |
58 |
|
argument should be a POSIX extended regular expression. The matching |
59 |
|
is case insensitive. |
60 |
|
|
61 |
|
For example, the following invocation |
62 |
|
|
63 |
|
%(reply_regex ^\(re|aw|ang|odp\)\(\\[[0-9]+\\]\)?:[[:blank:]]) |
64 |
|
|
65 |
|
corresponds to the English "Re", Polish "Odp", Norwegian "Aw" or |
66 |
|
German "Ang", optionally followed by a number in brackets, followed |
67 |
|
by colon and any amount of whitespace. Notice the quoting of the |
68 |
|
regex metacharacters. |
69 |
|
|
70 |
|
See also `Reply-Regex' and `isreply' below. |
71 |
|
|
72 |
|
*** isreply |
73 |
|
Argument: [OPTIONAL] string |
74 |
|
Return: boolean |
75 |
|
|
76 |
|
If argument is not given, the value of Subject: header is taken. |
77 |
|
|
78 |
|
The function returns true if its argument matches the "reply subject" |
79 |
|
regular expression. This expression is set via the global profile variable |
80 |
|
Reply-Regex or via the format function %(reply_regex). |
81 |
|
|
82 |
|
This function is useful for creating Subject: headers in reply |
83 |
|
messages. For example, consider the following construction: |
84 |
|
|
85 |
|
%<{subject}%(lit)%<(isreply)%?\ |
86 |
|
(profile reply-prefix)%(concat)%|%(concat Re:)%>\ |
87 |
|
%(concat{subject})%(printhdr Subject: )\n%> |
88 |
|
|
89 |
|
If the Subject: header already contained reply prefix, this construct |
90 |
|
leaves it unchanged. Otherwise it prepends to it the value of |
91 |
|
Reply-Prefix profile variable, or, if it is unset, the string "Re:". |
92 |
|
|
93 |
|
This expression is used in default replcomps and replgroupcomps files. |
94 |
|
|
95 |
*** rcpt |
*** rcpt |
96 |
Argument: string, one of "to", "cc", "me", "all" |
Argument: string, one of "to", "cc", "me", "all" |
97 |
Return: boolean |
Return: boolean |
120 |
it is split at whitespace characters nearest to the width boundary |
it is split at whitespace characters nearest to the width boundary |
121 |
and each subsequent segment is prefixed with horizontal tabulation. |
and each subsequent segment is prefixed with horizontal tabulation. |
122 |
|
|
|
|
|
123 |
*** in_reply_to |
*** in_reply_to |
124 |
Argument: none |
Argument: none |
125 |
Return: string |
Return: string |
132 |
|
|
133 |
Generates the value for the References: header according to RFC 2822. |
Generates the value for the References: header according to RFC 2822. |
134 |
|
|
135 |
|
* New profile variables: |
136 |
|
|
137 |
|
** Reply-Regex |
138 |
|
|
139 |
|
Sets the regular expression used to recognize reply messages. The |
140 |
|
argument should be a POSIX extended regular expression. The matching |
141 |
|
is case insensitive. |
142 |
|
|
143 |
|
For example, setting in your .mh_profile: |
144 |
|
|
145 |
|
Reply-Regex: ^(re|aw|ang|odp)(\[[0-9]+\])?:[[:blank:]] |
146 |
|
|
147 |
|
will make the default replcomps and replgroupcomps formats recognize |
148 |
|
usual English, Norwiegian, German and Polish reply subject prefixes. |
149 |
|
|
150 |
|
See also format functions `reply_regex' and `isreply'. |
151 |
|
|
152 |
* rmm |
* rmm |
153 |
|
|
154 |
** Different behaviour if one of the messages in the list does not exist. |
** Different behaviour if one of the messages in the list does not exist. |