|
0
|
1 \input texinfo @c -*-texinfo-*-
|
|
|
2
|
|
70
|
3 @setfilename ../info/message.info
|
|
|
4 @settitle Message Manual
|
|
0
|
5 @synindex fn cp
|
|
|
6 @synindex vr cp
|
|
|
7 @synindex pg cp
|
|
|
8 @iftex
|
|
|
9 @finalout
|
|
|
10 @end iftex
|
|
|
11 @setchapternewpage odd
|
|
|
12
|
|
|
13 @ifinfo
|
|
|
14
|
|
70
|
15 This file documents Messa, the Emacs message composition mode.
|
|
0
|
16
|
|
|
17 Copyright (C) 1996 Free Software Foundation, Inc.
|
|
|
18
|
|
|
19 Permission is granted to make and distribute verbatim copies of
|
|
|
20 this manual provided the copyright notice and this permission notice
|
|
|
21 are preserved on all copies.
|
|
|
22
|
|
|
23 @ignore
|
|
|
24 Permission is granted to process this file through Tex and print the
|
|
|
25 results, provided the printed document carries copying permission
|
|
|
26 notice identical to this one except for the removal of this paragraph
|
|
|
27 (this paragraph not being relevant to the printed manual).
|
|
|
28
|
|
|
29 @end ignore
|
|
|
30 Permission is granted to copy and distribute modified versions of this
|
|
|
31 manual under the conditions for verbatim copying, provided also that the
|
|
|
32 entire resulting derived work is distributed under the terms of a
|
|
|
33 permission notice identical to this one.
|
|
|
34
|
|
|
35 Permission is granted to copy and distribute translations of this manual
|
|
|
36 into another language, under the above conditions for modified versions.
|
|
|
37 @end ifinfo
|
|
|
38
|
|
|
39 @tex
|
|
|
40
|
|
|
41 @titlepage
|
|
70
|
42 @title Message Manual
|
|
0
|
43
|
|
|
44 @author by Lars Magne Ingebrigtsen
|
|
|
45 @page
|
|
|
46
|
|
|
47 @vskip 0pt plus 1filll
|
|
|
48 Copyright @copyright{} 1996 Free Software Foundation, Inc.
|
|
|
49
|
|
|
50 Permission is granted to make and distribute verbatim copies of
|
|
|
51 this manual provided the copyright notice and this permission notice
|
|
|
52 are preserved on all copies.
|
|
|
53
|
|
|
54 Permission is granted to copy and distribute modified versions of this
|
|
|
55 manual under the conditions for verbatim copying, provided that the
|
|
|
56 entire resulting derived work is distributed under the terms of a
|
|
|
57 permission notice identical to this one.
|
|
|
58
|
|
|
59 Permission is granted to copy and distribute translations of this manual
|
|
|
60 into another language, under the above conditions for modified versions.
|
|
|
61
|
|
|
62 @end titlepage
|
|
|
63 @page
|
|
|
64
|
|
|
65 @end tex
|
|
|
66
|
|
|
67 @node Top
|
|
|
68 @top Message
|
|
|
69
|
|
|
70 All message composition (both mail and news) takes place in Message mode
|
|
|
71 buffers.
|
|
|
72
|
|
|
73 @menu
|
|
|
74 * Interface:: Setting up message buffers.
|
|
|
75 * Commands:: Commands you can execute in message mode buffers.
|
|
|
76 * Variables:: Customizing the message buffers.
|
|
|
77 * Index:: Variable, function and concept index.
|
|
|
78 * Key Index:: List of Message mode keys.
|
|
|
79 @end menu
|
|
|
80
|
|
|
81
|
|
|
82 @node Interface
|
|
|
83 @chapter Interface
|
|
|
84
|
|
|
85 When a program (or a person) wants to respond to a message -- reply,
|
|
|
86 follow up, forward, cancel -- the program (or person) should just put
|
|
|
87 point in the buffer where the message is and call the required command.
|
|
|
88 @code{Message} will then pop up a new @code{message} mode buffer with
|
|
|
89 appropriate headers filled out, and the user can edit the message before
|
|
|
90 sending it.
|
|
|
91
|
|
|
92 @menu
|
|
|
93 * New Mail Message:: Editing a brand new mail message.
|
|
|
94 * New News Message:: Editing a brand new news message.
|
|
|
95 * Reply:: Replying via mail.
|
|
|
96 * Wide Reply:: Responding to all people via mail.
|
|
|
97 * Followup:: Following up via news.
|
|
|
98 * Canceling News:: Canceling a news article.
|
|
|
99 * Superseding:: Superseding a message.
|
|
|
100 * Forwarding:: Forwarding a message via news or mail.
|
|
|
101 * Resending:: Resending a mail message.
|
|
|
102 * Bouncing:: Bouncing a mail message.
|
|
|
103 @end menu
|
|
|
104
|
|
|
105
|
|
|
106 @node New Mail Message
|
|
|
107 @section New Mail Message
|
|
|
108
|
|
|
109 @findex message-mail
|
|
|
110 The @code{message-mail} command pops up a new message buffer.
|
|
|
111
|
|
|
112 Two optional parameters are accepted: The first will be used as the
|
|
|
113 @code{To} header and the second as the @code{Subject} header. If these
|
|
|
114 aren't present, those two headers will be empty.
|
|
|
115
|
|
|
116
|
|
|
117 @node New News Message
|
|
|
118 @section New News Message
|
|
|
119
|
|
|
120 @findex message-news
|
|
|
121 The @code{message-news} command pops up a new message buffer.
|
|
|
122
|
|
|
123 This function accepts two optional parameters. The first will be used
|
|
|
124 as the @code{Newsgroups} header and the second as the @code{Subject}
|
|
|
125 header. If these aren't present, those two headers will be empty.
|
|
|
126
|
|
|
127
|
|
|
128 @node Reply
|
|
|
129 @section Reply
|
|
|
130
|
|
|
131 @findex message-reply
|
|
|
132 The @code{message-reply} function pops up a message buffer that's a
|
|
|
133 reply to the message in the current buffer.
|
|
|
134
|
|
|
135 @vindex message-reply-to-function
|
|
|
136 Message uses the normal methods to determine where replies are to go,
|
|
|
137 but you can change the behavior to suit your needs by fiddling with the
|
|
|
138 @code{message-reply-to-function} variable.
|
|
|
139
|
|
|
140 If you want the replies to go to the @code{Sender} instead of the
|
|
|
141 @code{From}, you could do something like this:
|
|
|
142
|
|
|
143 @lisp
|
|
|
144 (setq message-reply-to-function
|
|
|
145 (lambda ()
|
|
|
146 (cond ((equal (mail-fetch-field "from") "somebody")
|
|
|
147 (mail-fetch-field "sender"))
|
|
|
148 (t
|
|
|
149 nil))))
|
|
|
150 @end lisp
|
|
|
151
|
|
|
152 This function will be called narrowed to the head of the article that is
|
|
|
153 being replied to.
|
|
|
154
|
|
|
155 As you can see, this function should return a string if it has an
|
|
|
156 opinion as to what the To header should be. If it does not, it should
|
|
|
157 just return @code{nil}, and the normal methods for determining the To
|
|
|
158 header will be used.
|
|
|
159
|
|
|
160 This function can also return a list. In that case, each list element
|
|
|
161 should be a cons, where the car should be the name of an header
|
|
|
162 (eg. @code{Cc}) and the cdr should be the header value
|
|
|
163 (eg. @samp{larsi@@ifi.uio.no}). All these headers will be inserted into
|
|
|
164 the head of the outgoing mail.
|
|
|
165
|
|
|
166
|
|
|
167 @node Wide Reply
|
|
|
168 @section Wide Reply
|
|
|
169
|
|
|
170 @findex message-wide-reply
|
|
|
171 The @code{message-wide-reply} pops up a message buffer that's a wide
|
|
70
|
172 reply to the message in the current buffer.
|
|
0
|
173
|
|
|
174 @vindex message-wide-reply-to-function
|
|
|
175 Message uses the normal methods to determine where wide replies are to go,
|
|
|
176 but you can change the behavior to suit your needs by fiddling with the
|
|
|
177 @code{message-wide-reply-to-function}. It is used in the same way as
|
|
|
178 @code{message-reply-to-function} (@pxref{Reply}).
|
|
|
179
|
|
|
180 @findex rmail-dont-reply-to-names
|
|
70
|
181 Addresses that matches the @code{rmail-dont-reply-to-names} regular
|
|
0
|
182 expression will be removed from the @code{Cc} header.
|
|
|
183
|
|
|
184
|
|
|
185 @node Followup
|
|
|
186 @section Followup
|
|
|
187
|
|
|
188 @findex message-followup
|
|
|
189 The @code{message-followup} command pops up a message buffer that's a
|
|
|
190 followup to the message in the current buffer.
|
|
|
191
|
|
|
192 @vindex message-followup-to-function
|
|
|
193 Message uses the normal methods to determine where followups are to go,
|
|
|
194 but you can change the behavior to suit your needs by fiddling with the
|
|
|
195 @code{message-followup-to-function}. It is used in the same way as
|
|
|
196 @code{message-reply-to-function} (@pxref{Reply}).
|
|
|
197
|
|
|
198 @vindex message-use-followup-to
|
|
|
199 The @code{message-use-followup-to} variable says what to do about
|
|
|
200 @code{Followup-To} headers. If it is @code{use}, always use the value.
|
|
|
201 If it is @code{ask} (which is the default), ask whether to use the
|
|
|
202 value. If it is @code{t}, use the value unless it is @samp{poster}. If
|
|
|
203 it is @code{nil}, don't use the value.
|
|
|
204
|
|
|
205
|
|
|
206 @node Canceling News
|
|
|
207 @section Canceling News
|
|
|
208
|
|
|
209 @findex message-cancel-news
|
|
|
210 The @code{message-cancel-news} command cancels the article in the
|
|
|
211 current buffer.
|
|
|
212
|
|
|
213
|
|
|
214 @node Superseding
|
|
|
215 @section Superseding
|
|
|
216
|
|
|
217 @findex message-supersede
|
|
|
218 The @code{message-supersede} command pops up a message buffer that will
|
|
|
219 supersede the message in the current buffer.
|
|
|
220
|
|
|
221 @vindex message-ignored-supersedes-headers
|
|
|
222 Headers matching the @code{message-ignored-supersedes-headers} are
|
|
70
|
223 removed before popping up the new message buffer. The default is
|
|
|
224 @samp{^Path:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|^Received:\\|^X-From-Line:\\|Return-Path:}.
|
|
0
|
225
|
|
|
226
|
|
|
227
|
|
|
228 @node Forwarding
|
|
|
229 @section Forwarding
|
|
|
230
|
|
|
231 @findex message-forward
|
|
|
232 The @code{message-forward} command pops up a message buffer to forward
|
|
|
233 the message in the current buffer. If given a prefix, forward using
|
|
|
234 news.
|
|
|
235
|
|
|
236 @table @code
|
|
|
237 @item message-forward-start-separator
|
|
|
238 @vindex message-forward-start-separator
|
|
70
|
239 Delimiter inserted before forwarded messages. The default is
|
|
0
|
240 @samp{------- Start of forwarded message -------\n}.
|
|
|
241
|
|
|
242 @vindex message-forward-end-separator
|
|
|
243 @item message-forward-end-separator
|
|
|
244 @vindex message-forward-end-separator
|
|
70
|
245 Delimiter inserted after forwarded messages. The default is
|
|
0
|
246 @samp{------- End of forwarded message -------\n}.
|
|
|
247
|
|
|
248 @item message-signature-before-forwarded-message
|
|
|
249 @vindex message-signature-before-forwarded-message
|
|
|
250 If this variable is @code{t}, which it is by default, your personal
|
|
|
251 signature will be inserted before the forwarded message. If not, the
|
|
|
252 forwarded message will be inserted first in the new mail.
|
|
|
253
|
|
|
254 @item message-included-forward-headers
|
|
|
255 @vindex message-included-forward-headers
|
|
|
256 Regexp matching header lines to be included in forwarded messages.
|
|
|
257
|
|
|
258 @end table
|
|
|
259
|
|
|
260
|
|
|
261 @node Resending
|
|
|
262 @section Resending
|
|
|
263
|
|
|
264 @findex message-resend
|
|
|
265 The @code{message-resend} command will prompt the user for an address
|
|
|
266 and resend the message in the current buffer to that address.
|
|
|
267
|
|
|
268 @vindex message-ignored-resent-headers
|
|
70
|
269 Headers the match the @code{message-ignored-resent-headers} regexp will
|
|
0
|
270 be removed before sending the message. The default is
|
|
|
271 @samp{^Return-receipt}.
|
|
|
272
|
|
|
273
|
|
|
274 @node Bouncing
|
|
|
275 @section Bouncing
|
|
|
276
|
|
|
277 @findex message-bounce
|
|
|
278 The @code{message-bounce} command will, if the current buffer contains a
|
|
|
279 bounced mail message, pop up a message buffer stripped of the bounce
|
|
70
|
280 information.
|
|
0
|
281
|
|
|
282 @vindex message-ignored-bounced-headers
|
|
|
283 Headers that match the @code{message-ignored-bounced-headers} regexp
|
|
|
284 will be removed before popping up the buffer. The default is
|
|
|
285 @samp{^Received:}.
|
|
|
286
|
|
|
287
|
|
|
288 @node Commands
|
|
|
289 @chapter Commands
|
|
|
290
|
|
|
291 @menu
|
|
|
292 * Header Commands:: Commands for moving to headers.
|
|
|
293 * Movement:: Moving around in message buffers.
|
|
|
294 * Insertion:: Inserting things into message buffers.
|
|
|
295 * Various Commands:: Various things.
|
|
|
296 * Sending:: Actually sending the message.
|
|
|
297 @end menu
|
|
|
298
|
|
|
299
|
|
|
300 @node Header Commands
|
|
|
301 @section Header Commands
|
|
|
302
|
|
|
303 All these commands move to the header in question. If it doesn't exist,
|
|
|
304 it will be inserted.
|
|
|
305
|
|
|
306 @table @kbd
|
|
|
307
|
|
|
308 @item C-c ?
|
|
|
309 @kindex C-c ?
|
|
|
310 @findex message-goto-to
|
|
|
311 Describe the message mode.
|
|
|
312
|
|
|
313 @item C-c C-f C-t
|
|
|
314 @kindex C-c C-f C-t
|
|
|
315 @findex message-goto-to
|
|
|
316 Go to the @code{To} header (@code{message-goto-to}).
|
|
|
317
|
|
|
318 @item C-c C-f C-b
|
|
|
319 @kindex C-c C-f C-b
|
|
|
320 @findex message-goto-bcc
|
|
|
321 Go to the @code{Bcc} header (@code{message-goto-bcc}).
|
|
|
322
|
|
|
323 @item C-c C-f C-f
|
|
|
324 @kindex C-c C-f C-f
|
|
|
325 @findex message-goto-fcc
|
|
|
326 Go to the @code{Fcc} header (@code{message-goto-fcc}).
|
|
|
327
|
|
|
328 @item C-c C-f C-c
|
|
|
329 @kindex C-c C-f C-c
|
|
|
330 @findex message-goto-cc
|
|
|
331 Go to the @code{Cc} header (@code{message-goto-cc}).
|
|
|
332
|
|
|
333 @item C-c C-f C-s
|
|
|
334 @kindex C-c C-f C-s
|
|
|
335 @findex message-goto-subject
|
|
|
336 Go to the @code{Subject} header (@code{message-goto-subject}).
|
|
|
337
|
|
|
338 @item C-c C-f C-r
|
|
|
339 @kindex C-c C-f C-r
|
|
|
340 @findex message-goto-reply-to
|
|
|
341 Go to the @code{Reply-To} header (@code{message-goto-reply-to}).
|
|
|
342
|
|
|
343 @item C-c C-f C-n
|
|
|
344 @kindex C-c C-f C-n
|
|
|
345 @findex message-goto-newsgroups
|
|
|
346 Go to the @code{Newsgroups} header (@code{message-goto-newsgroups}).
|
|
|
347
|
|
|
348 @item C-c C-f C-d
|
|
|
349 @kindex C-c C-f C-d
|
|
|
350 @findex message-goto-distribution
|
|
|
351 Go to the @code{Distribution} header (@code{message-goto-distribution}).
|
|
|
352
|
|
|
353 @item C-c C-f C-o
|
|
|
354 @kindex C-c C-f C-o
|
|
|
355 @findex message-goto-followup-to
|
|
|
356 Go to the @code{Followup-To} header (@code{message-goto-followup-to}).
|
|
|
357
|
|
|
358 @item C-c C-f C-k
|
|
|
359 @kindex C-c C-f C-k
|
|
|
360 @findex message-goto-keywords
|
|
|
361 Go to the @code{Keywords} header (@code{message-goto-keywords}).
|
|
|
362
|
|
|
363 @item C-c C-f C-u
|
|
|
364 @kindex C-c C-f C-u
|
|
|
365 @findex message-goto-summary
|
|
|
366 Go to the @code{Summary} header (@code{message-goto-summary}).
|
|
|
367
|
|
|
368 @end table
|
|
|
369
|
|
|
370
|
|
|
371 @node Movement
|
|
|
372 @section Movement
|
|
|
373
|
|
|
374 @table @kbd
|
|
|
375 @item C-c C-b
|
|
|
376 @kindex C-c C-b
|
|
|
377 @findex message-goto-body
|
|
|
378 Move to the beginning of the body of the message
|
|
|
379 (@code{message-goto-body}).
|
|
|
380
|
|
|
381 @item C-c C-i
|
|
|
382 @kindex C-c C-i
|
|
|
383 @findex message-goto-signature
|
|
|
384 Move to the signature of the message (@code{message-goto-signature}).
|
|
|
385
|
|
|
386 @end table
|
|
|
387
|
|
|
388
|
|
|
389 @node Insertion
|
|
|
390 @section Insertion
|
|
|
391
|
|
|
392 @table @kbd
|
|
|
393
|
|
|
394 @item C-c C-y
|
|
|
395 @kindex C-c C-y
|
|
|
396 @findex message-yank-original
|
|
|
397 Yank the message that's being replied to into the message buffer
|
|
|
398 (@code{message-yank-original}).
|
|
|
399
|
|
|
400 @item C-c C-q
|
|
|
401 @kindex C-c C-q
|
|
|
402 @findex message-fill-yanked-message
|
|
|
403 Fill the yanked message (@code{message-fill-yanked-message}).
|
|
|
404
|
|
|
405 @item C-c C-w
|
|
|
406 @kindex C-c C-w
|
|
|
407 @findex message-insert-signature
|
|
|
408 Insert a signature at the end of the buffer
|
|
|
409 (@code{message-insert-signature}).
|
|
|
410
|
|
|
411 @end table
|
|
|
412
|
|
|
413 @table @code
|
|
|
414 @item message-ignored-cited-headers
|
|
|
415 @vindex message-ignored-cited-headers
|
|
|
416 All headers that match this regexp will be removed from yanked
|
|
|
417 messages. The default is @samp{.}, which means that all headers will be
|
|
|
418 removed.
|
|
|
419
|
|
|
420 @item message-citation-line-function
|
|
|
421 @vindex message-citation-line-function
|
|
|
422 Function called to insert the citation line. The default is
|
|
|
423 @code{message-insert-citation-line}.
|
|
|
424
|
|
|
425 @item message-yank-prefix
|
|
|
426 @vindex message-yank-prefix
|
|
|
427 @cindex yanking
|
|
|
428 @cindex quoting
|
|
|
429 When you are replying to or following up an article, you normally want
|
|
|
430 to quote the person you are answering. Inserting quoted text is done by
|
|
|
431 @dfn{yanking}, and each quoted line you yank will have
|
|
|
432 @code{message-yank-prefix} prepended to it. The default is @samp{> }.
|
|
|
433 If it is @code{nil}, just indent the message.
|
|
|
434
|
|
|
435 @item message-indentation-spaces
|
|
|
436 @vindex message-indentation-spaces
|
|
|
437 Number of spaces to indent yanked messages.
|
|
|
438
|
|
|
439 @item message-cite-function
|
|
|
440 @vindex message-cite-function
|
|
|
441 @findex message-cite-original
|
|
|
442 @findex sc-cite-original
|
|
|
443 @cindex Supercite
|
|
|
444 Function for citing an original message. The default is
|
|
|
445 @code{message-cite-original}. You can also set it to
|
|
|
446 @code{sc-cite-original} to use Supercite.
|
|
|
447
|
|
|
448 @item message-indent-citation-function
|
|
|
449 @vindex message-indent-citation-function
|
|
|
450 Function for modifying a citation just inserted in the mail buffer.
|
|
|
451 This can also be a list of functions. Each function can find the
|
|
|
452 citation between @code{(point)} and @code{(mark t)}. And each function
|
|
|
453 should leave point and mark around the citation text as modified.
|
|
|
454
|
|
|
455 @item message-signature
|
|
|
456 @vindex message-signature
|
|
|
457 String to be inserted at the end of the message buffer. If @code{t}
|
|
|
458 (which is the default), the @code{message-signature-file} file will be
|
|
|
459 inserted instead. If a function, the result from the function will be
|
|
|
460 used instead. If a form, the result from the form will be used instead.
|
|
|
461 If this variable is @code{nil}, no signature will be inserted at all.
|
|
|
462
|
|
|
463 @item message-signature-file
|
|
|
464 @vindex message-signature-file
|
|
|
465 File containing the signature to be inserted at the end of the buffer.
|
|
|
466 The default is @samp{~/.signature}.
|
|
|
467
|
|
|
468 @end table
|
|
|
469
|
|
|
470 Note that RFC1036 says that a signature should be preceded by the three
|
|
|
471 characters @samp{-- } on a line by themselves. This is to make it
|
|
|
472 easier for the recipient to automatically recognize and process the
|
|
|
473 signature. So don't remove those characters, even though you might feel
|
|
70
|
474 that they ruin you beautiful design, like, totally.
|
|
0
|
475
|
|
|
476 Also note that no signature should be more than four lines long.
|
|
|
477 Including ASCII graphics is an efficient way to get everybody to believe
|
|
|
478 that you are silly and have nothing important to say.
|
|
|
479
|
|
|
480
|
|
|
481
|
|
|
482 @node Various Commands
|
|
|
483 @section Various Commands
|
|
|
484
|
|
|
485 @table @kbd
|
|
|
486
|
|
|
487 @item C-c C-r
|
|
|
488 @kindex C-c C-r
|
|
|
489 @findex message-caesar-buffer-body
|
|
|
490 Caesar rotate (aka. rot13) the current message
|
|
|
491 (@code{message-caesar-buffer-body}). If narrowing is in effect, just
|
|
|
492 rotate the visible portion of the buffer. A numerical prefix says how
|
|
|
493 many places to rotate the text. The default is 13.
|
|
|
494
|
|
|
495 @item C-c C-t
|
|
|
496 @kindex C-c C-t
|
|
|
497 @findex message-insert-to
|
|
|
498 Insert a @code{To} header that contains the @code{Reply-To} or
|
|
|
499 @code{From} header of the message you're following up
|
|
|
500 (@code{message-insert-to}).
|
|
|
501
|
|
|
502 @item C-c C-n
|
|
|
503 @kindex C-c C-n
|
|
|
504 @findex message-insert-newsgroups
|
|
|
505 Insert a @code{Newsgroups} header that reflects the @code{Followup-To}
|
|
|
506 or @code{Newsgroups} header of the article you're replying to
|
|
|
507 (@code{message-insert-newsgroups}).
|
|
|
508
|
|
|
509 @item C-c M-r
|
|
|
510 @kindex C-c M-r
|
|
|
511 @findex message-rename-buffer
|
|
|
512 Rename the buffer (@code{message-rename-buffer}). If given a prefix,
|
|
|
513 prompt for a new buffer name.
|
|
|
514
|
|
|
515 @end table
|
|
|
516
|
|
|
517
|
|
|
518 @node Sending
|
|
|
519 @section Sending
|
|
|
520
|
|
|
521 @table @kbd
|
|
|
522 @item C-c C-c
|
|
|
523 @kindex C-c C-c
|
|
|
524 @findex message-send-and-exit
|
|
|
525 Send the message and bury the current buffer
|
|
|
526 (@code{message-send-and-exit}).
|
|
|
527
|
|
|
528 @item C-c C-s
|
|
|
529 @kindex C-c C-s
|
|
|
530 @findex message-send
|
|
|
531 Send the message (@code{message-send}).
|
|
|
532
|
|
|
533 @item C-c C-d
|
|
|
534 @kindex C-c C-d
|
|
|
535 @findex message-dont-send
|
|
|
536 Bury the message buffer and exit (@code{message-dont-send}).
|
|
|
537
|
|
|
538 @item C-c C-k
|
|
|
539 @kindex C-c C-k
|
|
|
540 @findex message-kill-buffer
|
|
|
541 Kill the message buffer and exit (@code{message-kill-buffer}).
|
|
|
542
|
|
|
543 @end table
|
|
|
544
|
|
|
545
|
|
|
546 @node Variables
|
|
|
547 @chapter Variables
|
|
|
548
|
|
|
549 @menu
|
|
|
550 * Message Headers:: General message header stuff.
|
|
|
551 * Mail Headers:: Customizing mail headers.
|
|
|
552 * Mail Variables:: Other mail variables.
|
|
|
553 * News Headers:: Customizing news headers.
|
|
|
554 * News Variables:: Other news variables.
|
|
|
555 * Various Message Variables:: Other message variables.
|
|
|
556 * Sending Variables:: Variables for sending.
|
|
|
557 * Message Buffers:: How Message names its buffers.
|
|
|
558 * Message Actions:: Actions to be performed when exiting.
|
|
|
559 @end menu
|
|
|
560
|
|
|
561
|
|
|
562 @node Message Headers
|
|
|
563 @section Message Headers
|
|
|
564
|
|
|
565 Message is quite aggressive on the message generation front. It has
|
|
|
566 to be -- it's a combined news and mail agent. To be able to send
|
|
|
567 combined messages, it has to generate all headers itself to ensure that
|
|
|
568 mail and news copies of messages look sufficiently similar.
|
|
|
569
|
|
|
570 @table @code
|
|
|
571
|
|
|
572 @item message-generate-headers-first
|
|
|
573 @vindex message-generate-headers-first
|
|
|
574 If non-@code{nil}, generate all headers before starting to compose the
|
|
|
575 message.
|
|
|
576
|
|
|
577 @item message-from-style
|
|
|
578 @vindex message-from-style
|
|
|
579 Specifies how @code{From} headers should look. There are four legal
|
|
|
580 values:
|
|
|
581
|
|
|
582 @table @code
|
|
|
583 @item nil
|
|
|
584 Just the address -- @samp{king@@grassland.com}.
|
|
|
585
|
|
|
586 @item parens
|
|
|
587 @samp{king@@grassland.com (Elvis Parsley)}.
|
|
|
588
|
|
|
589 @item angles
|
|
|
590 @samp{Elvis Parsley <king@@grassland.com>}.
|
|
|
591
|
|
|
592 @item default
|
|
|
593 Look like @code{angles} if that doesn't require quoting, and
|
|
|
594 @code{parens} if it does. If even @code{parens} requires quoting, use
|
|
|
595 @code{angles} anyway.
|
|
|
596
|
|
|
597 @end table
|
|
|
598
|
|
|
599 @item message-deletable-headers
|
|
|
600 @vindex message-deletable-headers
|
|
|
601 Headers in this list that were previously generated by Message will be
|
|
|
602 deleted before posting. Let's say you post an article. Then you decide
|
|
|
603 to post it again to some other group, you naughty boy, so you jump back
|
|
|
604 to the @code{*post-buf*} buffer, edit the @code{Newsgroups} line, and
|
|
|
605 ship it off again. By default, this variable makes sure that the old
|
|
|
606 generated @code{Message-ID} is deleted, and a new one generated. If
|
|
|
607 this isn't done, the entire empire would probably crumble, anarchy would
|
|
|
608 prevail, and cats would start walking on two legs and rule the world.
|
|
|
609 Allegedly.
|
|
|
610
|
|
|
611 @item message-default-headers
|
|
|
612 @vindex message-default-headers
|
|
|
613 This string is inserted at the end of the headers in all message
|
|
|
614 buffers.
|
|
|
615
|
|
|
616 @end table
|
|
|
617
|
|
|
618
|
|
|
619 @node Mail Headers
|
|
|
620 @section Mail Headers
|
|
|
621
|
|
|
622 @table @code
|
|
|
623 @item message-required-mail-headers
|
|
|
624 @vindex message-required-mail-headers
|
|
70
|
625 See @pxref{News Headers} for the syntax of this variable. It is
|
|
0
|
626 @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines
|
|
|
627 (optional . X-Mailer))} by default.
|
|
|
628
|
|
|
629 @item message-ignored-mail-headers
|
|
|
630 @vindex message-ignored-mail-headers
|
|
|
631 Regexp of headers to be removed before mailing. The default is
|
|
|
632 @samp{^Gcc:\\|^Fcc:}.
|
|
|
633
|
|
|
634 @item message-default-mail-headers
|
|
|
635 @vindex message-default-mail-headers
|
|
|
636 This string is inserted at the end of the headers in all message
|
|
|
637 buffers that are initialized as mail.
|
|
|
638
|
|
|
639 @end table
|
|
|
640
|
|
|
641
|
|
|
642 @node Mail Variables
|
|
|
643 @section Mail Variables
|
|
|
644
|
|
|
645 @table @code
|
|
|
646 @item message-send-mail-function
|
|
|
647 @vindex message-send-mail-function
|
|
|
648 Function used to send the current buffer as mail. The default is
|
|
|
649 @code{message-send-mail-with-sendmail}. If you prefer using MH
|
|
|
650 instead, set this variable to @code{message-send-mail-with-mh}.
|
|
|
651
|
|
|
652 @end table
|
|
|
653
|
|
|
654
|
|
|
655 @node News Headers
|
|
|
656 @section News Headers
|
|
|
657
|
|
|
658 @vindex message-required-news-headers
|
|
|
659 @code{message-required-news-headers} a list of header symbols. These
|
|
|
660 headers will either be automatically generated, or, if that's
|
|
|
661 impossible, they will be prompted for. The following symbols are legal:
|
|
|
662
|
|
|
663 @table @code
|
|
|
664
|
|
|
665 @item From
|
|
|
666 @cindex From
|
|
|
667 @findex user-full-name
|
|
|
668 @findex user-mail-address
|
|
|
669 This required header will be filled out with the result of the
|
|
|
670 @code{message-make-from} function, which depends on the
|
|
|
671 @code{message-from-style}, @code{user-full-name},
|
|
|
672 @code{user-mail-address} variables.
|
|
|
673
|
|
|
674 @item Subject
|
|
|
675 @cindex Subject
|
|
|
676 This required header will be prompted for if not present already.
|
|
|
677
|
|
|
678 @item Newsgroups
|
|
|
679 @cindex Newsgroups
|
|
|
680 This required header says which newsgroups the article is to be posted
|
|
|
681 to. If it isn't present already, it will be prompted for.
|
|
|
682
|
|
|
683 @item Organization
|
|
|
684 @cindex organization
|
|
|
685 This optional header will be filled out depending on the
|
|
|
686 @code{message-user-organization} variable.
|
|
70
|
687 @code{message-user-organization-file} will be used if that variable is
|
|
|
688 @code{t}.
|
|
0
|
689
|
|
|
690 @item Lines
|
|
|
691 @cindex Lines
|
|
|
692 This optional header will be computed by Message.
|
|
|
693
|
|
|
694 @item Message-ID
|
|
|
695 @cindex Message-ID
|
|
|
696 @vindex mail-host-address
|
|
|
697 @findex system-name
|
|
|
698 @cindex Sun
|
|
|
699 This required header will be generated by Message. A unique ID will be
|
|
70
|
700 created based on date, time, user name and system name. Message will
|
|
0
|
701 use @code{mail-host-address} as the fully qualified domain name (FQDN)
|
|
70
|
702 of the machine if that variable is define. If not, it will use
|
|
0
|
703 @code{system-name}, which doesn't report a FQDN on some machines --
|
|
|
704 notably Suns.
|
|
|
705
|
|
|
706 @item X-Newsreader
|
|
|
707 @cindex X-Newsreader
|
|
|
708 This optional header will be filled out according to the
|
|
|
709 @code{message-newsreader} local variable.
|
|
|
710
|
|
|
711 @item X-Mailer
|
|
|
712 This optional header will be filled out according to the
|
|
|
713 @code{message-mailer} local variable, unless there already is an
|
|
|
714 @code{X-Newsreader} header present.
|
|
|
715
|
|
|
716 @item In-Reply-To
|
|
|
717 This optional header is filled out using the @code{Date} and @code{From}
|
|
70
|
718 header of the article being replied.
|
|
0
|
719
|
|
|
720 @item Expires
|
|
|
721 @cindex Expires
|
|
|
722 This extremely optional header will be inserted according to the
|
|
|
723 @code{message-expires} variable. It is highly deprecated and shouldn't
|
|
|
724 be used unless you know what you're doing.
|
|
|
725
|
|
|
726 @item Distribution
|
|
|
727 @cindex Distribution
|
|
|
728 This optional header is filled out according to the
|
|
|
729 @code{message-distribution-function} variable. It is a deprecated and
|
|
|
730 much misunderstood header.
|
|
|
731
|
|
|
732 @item Path
|
|
|
733 @cindex path
|
|
70
|
734 This extremely optional header should probably not ever be used.
|
|
0
|
735 However, some @emph{very} old servers require that this header is
|
|
|
736 present. @code{message-user-path} further controls how this
|
|
70
|
737 @code{Path} header is to look. If is is @code{nil}, the the server name
|
|
|
738 as the leaf node. If is is a string, use the string. If it is neither
|
|
0
|
739 a string nor @code{nil}, use the user name only. However, it is highly
|
|
|
740 unlikely that you should need to fiddle with this variable at all.
|
|
|
741 @end table
|
|
|
742
|
|
|
743 @findex yow
|
|
|
744 @cindex Mime-Version
|
|
|
745 In addition, you can enter conses into this list. The car of this cons
|
|
|
746 should be a symbol. This symbol's name is the name of the header, and
|
|
|
747 the cdr can either be a string to be entered verbatim as the value of
|
|
|
748 this header, or it can be a function to be called. This function should
|
|
|
749 return a string to be inserted. For instance, if you want to insert
|
|
|
750 @code{Mime-Version: 1.0}, you should enter @code{(Mime-Version . "1.0")}
|
|
|
751 into the list. If you want to insert a funny quote, you could enter
|
|
|
752 something like @code{(X-Yow . yow)} into the list. The function
|
|
|
753 @code{yow} will then be called without any arguments.
|
|
|
754
|
|
|
755 If the list contains a cons where the car of the cons is
|
|
|
756 @code{optional}, the cdr of this cons will only be inserted if it is
|
|
|
757 non-@code{nil}.
|
|
|
758
|
|
|
759 Other variables for customizing outgoing news articles:
|
|
|
760
|
|
|
761 @table @code
|
|
|
762
|
|
|
763 @item message-syntax-checks
|
|
|
764 @vindex message-syntax-checks
|
|
70
|
765 If non-@code{nil}, message will attempt to check the legality of the
|
|
0
|
766 headers, as well as some other stuff, before posting. You can control
|
|
|
767 the granularity of the check by adding or removing elements from this
|
|
|
768 list. Legal elements are:
|
|
|
769
|
|
|
770 @table @code
|
|
|
771 @item subject-cmsg
|
|
|
772 Check the subject for commands.
|
|
|
773 @item sender
|
|
|
774 @cindex Sender
|
|
|
775 Insert a new @code{Sender} header if the @code{From} header looks odd.
|
|
|
776 @item multiple-headers
|
|
|
777 Check for the existence of multiple equal headers.
|
|
|
778 @item sendsys
|
|
|
779 @cindex sendsys
|
|
|
780 Check for the existence of version and sendsys commands.
|
|
|
781 @item message-id
|
|
|
782 Check whether the @code{Message-ID} looks ok.
|
|
|
783 @item from
|
|
|
784 Check whether the @code{From} header seems nice.
|
|
|
785 @item long-lines
|
|
|
786 @cindex long lines
|
|
|
787 Check for too long lines.
|
|
|
788 @item control-chars
|
|
|
789 Check for illegal characters.
|
|
|
790 @item size
|
|
|
791 Check for excessive size.
|
|
|
792 @item new-text
|
|
|
793 Check whether there is any new text in the messages.
|
|
|
794 @item signature
|
|
|
795 Check the length of the signature.
|
|
|
796 @item approved
|
|
|
797 @cindex approved
|
|
|
798 Check whether the article has an @code{Approved} header, which is
|
|
|
799 something only moderators should include.
|
|
|
800 @item empty
|
|
|
801 Check whether the article is empty.
|
|
|
802 @item empty-headers
|
|
|
803 Check whether any of the headers are empty.
|
|
|
804 @item existing-newsgroups
|
|
70
|
805 Check whether the newsgroups mentioned in the Newsgroups and
|
|
|
806 Followup-To headers exist.
|
|
0
|
807 @item valid-newsgroups
|
|
70
|
808 Check whether the @code{Newsgroups} and @code{Followup-To} headers
|
|
|
809 are valid syntactially.
|
|
0
|
810 @end table
|
|
|
811
|
|
|
812 All these conditions are checked by default.
|
|
|
813
|
|
|
814 @item message-ignored-news-headers
|
|
|
815 @vindex message-ignored-news-headers
|
|
70
|
816 Regexp of headers to be removed before posting. The default is
|
|
|
817 @samp{^NNTP-Posting-Host:\\|^Xref:\\|^Bcc:\\|^Gcc:\\|^Fcc:}.
|
|
0
|
818
|
|
|
819 @item message-default-news-headers
|
|
|
820 @vindex message-default-news-headers
|
|
|
821 This string is inserted at the end of the headers in all message
|
|
|
822 buffers that are initialized as news.
|
|
|
823
|
|
|
824 @end table
|
|
|
825
|
|
|
826
|
|
|
827 @node News Variables
|
|
|
828 @section News Variables
|
|
|
829
|
|
|
830 @table @code
|
|
|
831 @item message-send-news-function
|
|
|
832 @vindex message-send-news-function
|
|
|
833 Function used to send the current buffer as news. The default is
|
|
|
834 @code{message-send-news}.
|
|
|
835
|
|
|
836 @item message-post-method
|
|
|
837 @vindex message-post-method
|
|
|
838 Method used for posting a prepared news message.
|
|
|
839
|
|
|
840 @end table
|
|
|
841
|
|
|
842
|
|
|
843 @node Various Message Variables
|
|
|
844 @section Various Message Variables
|
|
|
845
|
|
|
846 @table @code
|
|
|
847 @item message-signature-separator
|
|
|
848 @vindex message-signature-separator
|
|
|
849 Regexp matching the signature separator. It is @samp{^-- *$} by
|
|
|
850 default.
|
|
|
851
|
|
|
852 @item mail-header-separator
|
|
|
853 @vindex mail-header-separator
|
|
|
854 String used to separate the headers from the body. It is @samp{--text
|
|
|
855 follows this line--} by default.
|
|
|
856
|
|
|
857 @item message-directory
|
|
|
858 @vindex message-directory
|
|
|
859 Directory used by many mailey things. The default is @file{~/Mail/}.
|
|
|
860
|
|
|
861 @item message-autosave-directory
|
|
|
862 @vindex message-autosave-directory
|
|
|
863 Directory where message buffers will be autosaved to.
|
|
|
864
|
|
|
865 @item message-signature-setup-hook
|
|
|
866 @vindex message-signature-setup-hook
|
|
|
867 Hook run when initializing the message buffer. It is run after the
|
|
|
868 headers have been inserted but before the signature has been inserted.
|
|
|
869
|
|
|
870 @item message-setup-hook
|
|
|
871 @vindex message-setup-hook
|
|
|
872 Hook run as the last thing when the message buffer has been initialized.
|
|
|
873
|
|
|
874 @item message-header-setup-hook
|
|
|
875 @vindex message-header-setup-hook
|
|
|
876 Hook called narrowed to the headers after initializing the headers.
|
|
|
877
|
|
|
878 @item message-send-hook
|
|
|
879 @vindex message-send-hook
|
|
|
880 Hook run before sending messages.
|
|
|
881
|
|
|
882 @item message-sent-hook
|
|
|
883 @vindex message-sent-hook
|
|
|
884 Hook run after sending messages.
|
|
|
885
|
|
|
886 @item message-mode-syntax-table
|
|
|
887 @vindex message-mode-syntax-table
|
|
|
888 Syntax table used in message mode buffers.
|
|
|
889
|
|
|
890 @end table
|
|
|
891
|
|
|
892
|
|
|
893
|
|
|
894 @node Sending Variables
|
|
|
895 @section Sending Variables
|
|
|
896
|
|
|
897 @table @code
|
|
|
898
|
|
|
899 @item message-fcc-handler-function
|
|
|
900 @vindex message-fcc-handler-function
|
|
|
901 A function called to save outgoing articles. This function will be
|
|
|
902 called with the name of the file to store the article in. The default
|
|
|
903 function is @code{rmail-output} which saves in Unix mailbox format.
|
|
|
904
|
|
|
905 @item message-courtesy-message
|
|
|
906 @vindex message-courtesy-message
|
|
|
907 When sending combined messages, this string is inserted at the start of
|
|
70
|
908 the mailed copy. If this variable is @code{nil}, no such courtesy
|
|
|
909 message will be added.
|
|
0
|
910
|
|
|
911 @end table
|
|
|
912
|
|
|
913
|
|
|
914 @node Message Buffers
|
|
|
915 @section Message Buffers
|
|
|
916
|
|
|
917 Message will generate new buffers with unique buffer names when you
|
|
|
918 request a message buffer. When you send the message, the buffer isn't
|
|
70
|
919 normally killed off. It's name is changed and a certain number of old
|
|
0
|
920 message buffers are kept alive.
|
|
|
921
|
|
|
922 @table @code
|
|
|
923 @item message-generate-new-buffers
|
|
|
924 @vindex message-generate-new-buffers
|
|
|
925 If non-@code{nil}, generate new buffers. The default is @code{t}. If
|
|
|
926 this is a function, call that function with three parameters: The type,
|
|
|
927 the to address and the group name. (Any of these may be @code{nil}.)
|
|
|
928 The function should return the new buffer name.
|
|
|
929
|
|
|
930 @item message-max-buffers
|
|
|
931 @vindex message-max-buffers
|
|
|
932 This variable says how many old message buffers to keep. If there are
|
|
|
933 more message buffers than this, the oldest buffer will be killed. The
|
|
|
934 default is 10. If this variable is @code{nil}, no old message buffers
|
|
|
935 will ever be killed.
|
|
|
936
|
|
|
937 @item message-send-rename-function
|
|
|
938 @vindex message-send-rename-function
|
|
|
939 After sending a message, the buffer is renamed from, for instance,
|
|
|
940 @samp{*reply to Lars*} to @samp{*sent reply to Lars*}. If you don't
|
|
|
941 like this, set this variable to a function that renames the buffer in a
|
|
|
942 manner you like. If you don't want to rename the buffer at all, you can
|
|
|
943 say:
|
|
|
944
|
|
|
945 @lisp
|
|
|
946 (setq message-send-rename-function 'ignore)
|
|
|
947 @end lisp
|
|
|
948
|
|
|
949 @item message-kill-buffer-on-exit
|
|
|
950 @findex message-kill-buffer-on-exit
|
|
|
951 If non-@code{nil}, kill the buffer immediately on exit.
|
|
|
952
|
|
|
953 @end table
|
|
|
954
|
|
|
955
|
|
|
956 @node Message Actions
|
|
|
957 @section Message Actions
|
|
|
958
|
|
|
959 When Message is being used from a news/mail reader, the reader is likely
|
|
|
960 to want to perform some task after the message has been sent. Perhaps
|
|
|
961 return to the previous window configuration or mark an article as
|
|
|
962 replied.
|
|
|
963
|
|
|
964 @vindex message-kill-actions
|
|
|
965 @vindex message-postpone-actions
|
|
|
966 @vindex message-exit-actions
|
|
|
967 @vindex message-send-actions
|
|
|
968 The user may exit from the message buffer in various ways. The most
|
|
|
969 common is @kbd{C-c C-c}, which sends the message and exits. Other
|
|
|
970 possibilities are @kbd{C-c C-s} which just sends the message, @kbd{C-c
|
|
|
971 C-d} which postpones the message editing and buries the message buffer,
|
|
|
972 and @kbd{C-c C-k} which kills the message buffer. Each of these actions
|
|
|
973 have lists associated with them that contains actions to be executed:
|
|
|
974 @code{message-send-actions}, @code{message-exit-actions},
|
|
|
975 @code{message-postpone-actions}, and @code{message-kill-actions}.
|
|
|
976
|
|
|
977 Message provides a function to interface with these lists:
|
|
|
978 @code{message-add-action}. The first parameter is the action to be
|
|
|
979 added, and the rest of the arguments are which lists to add this action
|
|
|
980 to. Here's an example from Gnus:
|
|
|
981
|
|
|
982 @lisp
|
|
|
983 (message-add-action
|
|
|
984 `(set-window-configuration ,(current-window-configuration))
|
|
|
985 'exit 'postpone 'kill)
|
|
|
986 @end lisp
|
|
|
987
|
|
|
988 This restores the Gnus window configuration when the message buffer is
|
|
|
989 killed, postponed or exited.
|
|
|
990
|
|
70
|
991 An @dfn{action} can be either a normal function; or a list where the
|
|
|
992 @code{car} is a function and the @code{cdr} is the list of arguments; or
|
|
0
|
993 a form to be @code{eval}ed.
|
|
|
994
|
|
|
995 @node Index
|
|
|
996 @chapter Index
|
|
|
997 @printindex cp
|
|
|
998
|
|
|
999 @node Key Index
|
|
|
1000 @chapter Key Index
|
|
|
1001 @printindex ky
|
|
|
1002
|
|
|
1003 @summarycontents
|
|
|
1004 @contents
|
|
|
1005 @bye
|
|
|
1006
|
|
|
1007 @c End:
|
