1 \input texinfo @c -*-texinfo-*-
4 @settitle Message Manual
11 @setchapternewpage odd
15 This file documents Messa, the Emacs message composition mode.
17 Copyright (C) 1996 Free Software Foundation, Inc.
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.
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).
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.
35 Permission is granted to copy and distribute translations of this manual
36 into another language, under the above conditions for modified versions.
44 @author by Lars Magne Ingebrigtsen
47 @vskip 0pt plus 1filll
48 Copyright @copyright{} 1996 Free Software Foundation, Inc.
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.
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.
59 Permission is granted to copy and distribute translations of this manual
60 into another language, under the above conditions for modified versions.
70 All message composition (both mail and news) takes place in Message mode
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.
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
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.
106 @node New Mail Message
107 @section New Mail Message
110 The @code{message-mail} command pops up a new message buffer.
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.
117 @node New News Message
118 @section New News Message
121 The @code{message-news} command pops up a new message buffer.
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.
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.
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.
140 If you want the replies to go to the @code{Sender} instead of the
141 @code{From}, you could do something like this:
144 (setq message-reply-to-function
146 (cond ((equal (mail-fetch-field "from") "somebody")
147 (mail-fetch-field "sender"))
152 This function will be called narrowed to the head of the article that is
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
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.
170 @findex message-wide-reply
171 The @code{message-wide-reply} pops up a message buffer that's a wide
172 reply to the message in the current buffer. A @dfn{wide reply} is a
173 reply that goes out to all people listed in the @code{To}, @code{From}
174 and @code{Cc} headers.
176 @vindex message-wide-reply-to-function
177 Message uses the normal methods to determine where wide replies are to go,
178 but you can change the behavior to suit your needs by fiddling with the
179 @code{message-wide-reply-to-function}. It is used in the same way as
180 @code{message-reply-to-function} (@pxref{Reply}).
182 @findex rmail-dont-reply-to-names
183 Addresses that match the @code{rmail-dont-reply-to-names} regular
184 expression will be removed from the @code{Cc} header.
190 @findex message-followup
191 The @code{message-followup} command pops up a message buffer that's a
192 followup to the message in the current buffer.
194 @vindex message-followup-to-function
195 Message uses the normal methods to determine where followups are to go,
196 but you can change the behavior to suit your needs by fiddling with the
197 @code{message-followup-to-function}. It is used in the same way as
198 @code{message-reply-to-function} (@pxref{Reply}).
200 @vindex message-use-followup-to
201 The @code{message-use-followup-to} variable says what to do about
202 @code{Followup-To} headers. If it is @code{use}, always use the value.
203 If it is @code{ask} (which is the default), ask whether to use the
204 value. If it is @code{t}, use the value unless it is @samp{poster}. If
205 it is @code{nil}, don't use the value.
209 @section Canceling News
211 @findex message-cancel-news
212 The @code{message-cancel-news} command cancels the article in the
219 @findex message-supersede
220 The @code{message-supersede} command pops up a message buffer that will
221 supersede the message in the current buffer.
223 @vindex message-ignored-supersedes-headers
224 Headers matching the @code{message-ignored-supersedes-headers} are
225 removed before popping up the new message buffer. The default is@*
226 @samp{^Path:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|@*
227 ^Received:\\|^X-From-Line:\\|Return-Path:}.
234 @findex message-forward
235 The @code{message-forward} command pops up a message buffer to forward
236 the message in the current buffer. If given a prefix, forward using
240 @item message-forward-start-separator
241 @vindex message-forward-start-separator
242 Delimiter inserted before forwarded messages. The default is@*
243 @samp{------- Start of forwarded message -------\n}.
245 @vindex message-forward-end-separator
246 @item message-forward-end-separator
247 @vindex message-forward-end-separator
248 Delimiter inserted after forwarded messages. The default is@*
249 @samp{------- End of forwarded message -------\n}.
251 @item message-signature-before-forwarded-message
252 @vindex message-signature-before-forwarded-message
253 If this variable is @code{t}, which it is by default, your personal
254 signature will be inserted before the forwarded message. If not, the
255 forwarded message will be inserted first in the new mail.
257 @item message-included-forward-headers
258 @vindex message-included-forward-headers
259 Regexp matching header lines to be included in forwarded messages.
267 @findex message-resend
268 The @code{message-resend} command will prompt the user for an address
269 and resend the message in the current buffer to that address.
271 @vindex message-ignored-resent-headers
272 Headers that match the @code{message-ignored-resent-headers} regexp will
273 be removed before sending the message. The default is
274 @samp{^Return-receipt}.
280 @findex message-bounce
281 The @code{message-bounce} command will, if the current buffer contains a
282 bounced mail message, pop up a message buffer stripped of the bounce
283 information. A @dfn{bounced message} is typically a mail you've sent
284 out that has been returned by some @code{mailer-daemon} as
287 @vindex message-ignored-bounced-headers
288 Headers that match the @code{message-ignored-bounced-headers} regexp
289 will be removed before popping up the buffer. The default is
297 * Header Commands:: Commands for moving to headers.
298 * Movement:: Moving around in message buffers.
299 * Insertion:: Inserting things into message buffers.
300 * Various Commands:: Various things.
301 * Sending:: Actually sending the message.
302 * Mail Aliases:: How to use mail aliases.
306 @node Header Commands
307 @section Header Commands
309 All these commands move to the header in question. If it doesn't exist,
316 @findex message-goto-to
317 Describe the message mode.
321 @findex message-goto-to
322 Go to the @code{To} header (@code{message-goto-to}).
326 @findex message-goto-bcc
327 Go to the @code{Bcc} header (@code{message-goto-bcc}).
331 @findex message-goto-fcc
332 Go to the @code{Fcc} header (@code{message-goto-fcc}).
336 @findex message-goto-cc
337 Go to the @code{Cc} header (@code{message-goto-cc}).
341 @findex message-goto-subject
342 Go to the @code{Subject} header (@code{message-goto-subject}).
346 @findex message-goto-reply-to
347 Go to the @code{Reply-To} header (@code{message-goto-reply-to}).
351 @findex message-goto-newsgroups
352 Go to the @code{Newsgroups} header (@code{message-goto-newsgroups}).
356 @findex message-goto-distribution
357 Go to the @code{Distribution} header (@code{message-goto-distribution}).
361 @findex message-goto-followup-to
362 Go to the @code{Followup-To} header (@code{message-goto-followup-to}).
366 @findex message-goto-keywords
367 Go to the @code{Keywords} header (@code{message-goto-keywords}).
371 @findex message-goto-summary
372 Go to the @code{Summary} header (@code{message-goto-summary}).
383 @findex message-goto-body
384 Move to the beginning of the body of the message
385 (@code{message-goto-body}).
389 @findex message-goto-signature
390 Move to the signature of the message (@code{message-goto-signature}).
402 @findex message-yank-original
403 Yank the message that's being replied to into the message buffer
404 (@code{message-yank-original}).
408 @findex message-fill-yanked-message
409 Fill the yanked message (@code{message-fill-yanked-message}).
413 @findex message-insert-signature
414 Insert a signature at the end of the buffer
415 (@code{message-insert-signature}).
420 @item message-ignored-cited-headers
421 @vindex message-ignored-cited-headers
422 All headers that match this regexp will be removed from yanked
423 messages. The default is @samp{.}, which means that all headers will be
426 @item message-citation-line-function
427 @vindex message-citation-line-function
428 Function called to insert the citation line. The default is
429 @code{message-insert-citation-line}.
431 @item message-yank-prefix
432 @vindex message-yank-prefix
435 When you are replying to or following up an article, you normally want
436 to quote the person you are answering. Inserting quoted text is done by
437 @dfn{yanking}, and each quoted line you yank will have
438 @code{message-yank-prefix} prepended to it. The default is @samp{> }.
439 If it is @code{nil}, just indent the message.
441 @item message-indentation-spaces
442 @vindex message-indentation-spaces
443 Number of spaces to indent yanked messages.
445 @item message-cite-function
446 @vindex message-cite-function
447 @findex message-cite-original
448 @findex sc-cite-original
450 Function for citing an original message. The default is
451 @code{message-cite-original}. You can also set it to
452 @code{sc-cite-original} to use Supercite.
454 @item message-indent-citation-function
455 @vindex message-indent-citation-function
456 Function for modifying a citation just inserted in the mail buffer.
457 This can also be a list of functions. Each function can find the
458 citation between @code{(point)} and @code{(mark t)}. And each function
459 should leave point and mark around the citation text as modified.
461 @item message-signature
462 @vindex message-signature
463 String to be inserted at the end of the message buffer. If @code{t}
464 (which is the default), the @code{message-signature-file} file will be
465 inserted instead. If a function, the result from the function will be
466 used instead. If a form, the result from the form will be used instead.
467 If this variable is @code{nil}, no signature will be inserted at all.
469 @item message-signature-file
470 @vindex message-signature-file
471 File containing the signature to be inserted at the end of the buffer.
472 The default is @samp{~/.signature}.
476 Note that RFC1036 says that a signature should be preceded by the three
477 characters @samp{-- } on a line by themselves. This is to make it
478 easier for the recipient to automatically recognize and process the
479 signature. So don't remove those characters, even though you might feel
480 that they ruin your beautiful design, like, totally.
482 Also note that no signature should be more than four lines long.
483 Including ASCII graphics is an efficient way to get everybody to believe
484 that you are silly and have nothing important to say.
488 @node Various Commands
489 @section Various Commands
495 @findex message-caesar-buffer-body
496 Caesar rotate (aka. rot13) the current message
497 (@code{message-caesar-buffer-body}). If narrowing is in effect, just
498 rotate the visible portion of the buffer. A numerical prefix says how
499 many places to rotate the text. The default is 13.
503 @findex message-elide-region
504 Elide the text between point and mark (@code{message-elide-region}).
505 The text is killed and an ellipsis (@samp{[...]}) will be inserted in
510 @findex message-insert-to
511 Insert a @code{To} header that contains the @code{Reply-To} or
512 @code{From} header of the message you're following up
513 (@code{message-insert-to}).
517 @findex message-insert-newsgroups
518 Insert a @code{Newsgroups} header that reflects the @code{Followup-To}
519 or @code{Newsgroups} header of the article you're replying to
520 (@code{message-insert-newsgroups}).
524 @findex message-rename-buffer
525 Rename the buffer (@code{message-rename-buffer}). If given a prefix,
526 prompt for a new buffer name.
537 @findex message-send-and-exit
538 Send the message and bury the current buffer
539 (@code{message-send-and-exit}).
544 Send the message (@code{message-send}).
548 @findex message-dont-send
549 Bury the message buffer and exit (@code{message-dont-send}).
553 @findex message-kill-buffer
554 Kill the message buffer and exit (@code{message-kill-buffer}).
561 @section Mail Aliases
565 Message uses @code{mailabbrev} to handle mail aliases.
566 @code{mailabbrev} works by parsing the @file{/etc/mailrc} and
567 @file{~/.mailrc} files. These files look like:
570 alias lmi "Lars Magne Ingebrigtsen <larsi@@ifi.uio.no>"
571 alias ding "ding@@ifi.uio.no (ding mailing list)"
574 After adding lines like this to your @file{~/.mailrc} file, you should
575 be able to just write @samp{lmi} in the @code{To} or @code{Cc} (and so
576 on) headers and press @kbd{SPC} to expand the alias.
578 No expansion will be performed upon sending of the message---all
579 expansions have to be done explicitly.
587 * Message Headers:: General message header stuff.
588 * Mail Headers:: Customizing mail headers.
589 * Mail Variables:: Other mail variables.
590 * News Headers:: Customizing news headers.
591 * News Variables:: Other news variables.
592 * Various Message Variables:: Other message variables.
593 * Sending Variables:: Variables for sending.
594 * Message Buffers:: How Message names its buffers.
595 * Message Actions:: Actions to be performed when exiting.
599 @node Message Headers
600 @section Message Headers
602 Message is quite aggressive on the message generation front. It has
603 to be -- it's a combined news and mail agent. To be able to send
604 combined messages, it has to generate all headers itself to ensure that
605 mail and news copies of messages look sufficiently similar.
609 @item message-generate-headers-first
610 @vindex message-generate-headers-first
611 If non-@code{nil}, generate all headers before starting to compose the
614 @item message-from-style
615 @vindex message-from-style
616 Specifies how @code{From} headers should look. There are four legal
621 Just the address -- @samp{king@@grassland.com}.
624 @samp{king@@grassland.com (Elvis Parsley)}.
627 @samp{Elvis Parsley <king@@grassland.com>}.
630 Look like @code{angles} if that doesn't require quoting, and
631 @code{parens} if it does. If even @code{parens} requires quoting, use
632 @code{angles} anyway.
636 @item message-deletable-headers
637 @vindex message-deletable-headers
638 Headers in this list that were previously generated by Message will be
639 deleted before posting. Let's say you post an article. Then you decide
640 to post it again to some other group, you naughty boy, so you jump back
641 to the @code{*post-buf*} buffer, edit the @code{Newsgroups} line, and
642 ship it off again. By default, this variable makes sure that the old
643 generated @code{Message-ID} is deleted, and a new one generated. If
644 this isn't done, the entire empire would probably crumble, anarchy would
645 prevail, and cats would start walking on two legs and rule the world.
648 @item message-default-headers
649 @vindex message-default-headers
650 This string is inserted at the end of the headers in all message
657 @section Mail Headers
660 @item message-required-mail-headers
661 @vindex message-required-mail-headers
662 @xref{News Headers}, for the syntax of this variable. It is
663 @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines
664 (optional . X-Mailer))} by default.
666 @item message-ignored-mail-headers
667 @vindex message-ignored-mail-headers
668 Regexp of headers to be removed before mailing. The default is
669 @samp{^Gcc:\\|^Fcc:}.
671 @item message-default-mail-headers
672 @vindex message-default-mail-headers
673 This string is inserted at the end of the headers in all message
674 buffers that are initialized as mail.
680 @section Mail Variables
683 @item message-send-mail-function
684 @vindex message-send-mail-function
685 Function used to send the current buffer as mail. The default is
686 @code{message-send-mail-with-sendmail}. If you prefer using MH
687 instead, set this variable to @code{message-send-mail-with-mh}.
693 @section News Headers
695 @vindex message-required-news-headers
696 @code{message-required-news-headers} a list of header symbols. These
697 headers will either be automatically generated, or, if that's
698 impossible, they will be prompted for. The following symbols are legal:
704 @findex user-full-name
705 @findex user-mail-address
706 This required header will be filled out with the result of the
707 @code{message-make-from} function, which depends on the
708 @code{message-from-style}, @code{user-full-name},
709 @code{user-mail-address} variables.
713 This required header will be prompted for if not present already.
717 This required header says which newsgroups the article is to be posted
718 to. If it isn't present already, it will be prompted for.
722 This optional header will be filled out depending on the
723 @code{message-user-organization} variable.
724 @code{message-user-organization-file} will be used if this variable is
725 @code{t}. This variable can also be a string (in which case this string
726 will be used), or it can be a function (which will be called with no
727 parameters and should return a string to be used).
731 This optional header will be computed by Message.
735 @vindex mail-host-address
738 This required header will be generated by Message. A unique ID will be
739 created based on the date, time, user name and system name. Message will
740 use @code{mail-host-address} as the fully qualified domain name (FQDN)
741 of the machine if that variable is defined. If not, it will use
742 @code{system-name}, which doesn't report a FQDN on some machines --
747 This optional header will be filled out according to the
748 @code{message-newsreader} local variable.
751 This optional header will be filled out according to the
752 @code{message-mailer} local variable, unless there already is an
753 @code{X-Newsreader} header present.
756 This optional header is filled out using the @code{Date} and @code{From}
757 header of the article being replied to.
761 This extremely optional header will be inserted according to the
762 @code{message-expires} variable. It is highly deprecated and shouldn't
763 be used unless you know what you're doing.
767 This optional header is filled out according to the
768 @code{message-distribution-function} variable. It is a deprecated and
769 much misunderstood header.
773 This extremely optional header should probably never be used.
774 However, some @emph{very} old servers require that this header is
775 present. @code{message-user-path} further controls how this
776 @code{Path} header is to look. If it is @code{nil}, use the server name
777 as the leaf node. If it is a string, use the string. If it is neither
778 a string nor @code{nil}, use the user name only. However, it is highly
779 unlikely that you should need to fiddle with this variable at all.
784 In addition, you can enter conses into this list. The car of this cons
785 should be a symbol. This symbol's name is the name of the header, and
786 the cdr can either be a string to be entered verbatim as the value of
787 this header, or it can be a function to be called. This function should
788 return a string to be inserted. For instance, if you want to insert
789 @code{Mime-Version: 1.0}, you should enter @code{(Mime-Version . "1.0")}
790 into the list. If you want to insert a funny quote, you could enter
791 something like @code{(X-Yow . yow)} into the list. The function
792 @code{yow} will then be called without any arguments.
794 If the list contains a cons where the car of the cons is
795 @code{optional}, the cdr of this cons will only be inserted if it is
798 Other variables for customizing outgoing news articles:
802 @item message-syntax-checks
803 @vindex message-syntax-checks
804 If non-@code{nil}, Message will attempt to check the legality of the
805 headers, as well as some other stuff, before posting. You can control
806 the granularity of the check by adding or removing elements from this
807 list. Legal elements are:
811 Check the subject for commands.
814 Insert a new @code{Sender} header if the @code{From} header looks odd.
815 @item multiple-headers
816 Check for the existence of multiple equal headers.
819 Check for the existence of version and sendsys commands.
821 Check whether the @code{Message-ID} looks ok.
823 Check whether the @code{From} header seems nice.
826 Check for too long lines.
828 Check for illegal characters.
830 Check for excessive size.
832 Check whether there is any new text in the messages.
834 Check the length of the signature.
837 Check whether the article has an @code{Approved} header, which is
838 something only moderators should include.
840 Check whether the article is empty.
842 Check whether any of the headers are empty.
843 @item existing-newsgroups
844 Check whether the newsgroups mentioned in the @code{Newsgroups} and
845 @code{Followup-To} headers exist.
846 @item valid-newsgroups
847 Check whether the @code{Newsgroups} and @code{Followup-to} headers
848 are valid syntactically.
849 @item shorten-followup-to
850 Check whether to add a @code{Followup-to} header to shorten the number
851 of groups to post to.
854 All these conditions are checked by default.
856 @item message-ignored-news-headers
857 @vindex message-ignored-news-headers
858 Regexp of headers to be removed before posting. The default is@*
859 @samp{^NNTP-Posting-Host:\\|^Xref:\\|^Bcc:\\|^Gcc:\\|^Fcc:}.
861 @item message-default-news-headers
862 @vindex message-default-news-headers
863 This string is inserted at the end of the headers in all message
864 buffers that are initialized as news.
870 @section News Variables
873 @item message-send-news-function
874 @vindex message-send-news-function
875 Function used to send the current buffer as news. The default is
876 @code{message-send-news}.
878 @item message-post-method
879 @vindex message-post-method
880 Method used for posting a prepared news message.
885 @node Various Message Variables
886 @section Various Message Variables
889 @item message-signature-separator
890 @vindex message-signature-separator
891 Regexp matching the signature separator. It is @samp{^-- *$} by
894 @item mail-header-separator
895 @vindex mail-header-separator
896 String used to separate the headers from the body. It is @samp{--text
897 follows this line--} by default.
899 @item message-directory
900 @vindex message-directory
901 Directory used by many mailey things. The default is @file{~/Mail/}.
903 @item message-autosave-directory
904 @vindex message-autosave-directory
905 Directory where message buffers will be autosaved to.
907 @item message-signature-setup-hook
908 @vindex message-signature-setup-hook
909 Hook run when initializing the message buffer. It is run after the
910 headers have been inserted but before the signature has been inserted.
912 @item message-setup-hook
913 @vindex message-setup-hook
914 Hook run as the last thing when the message buffer has been initialized.
916 @item message-header-setup-hook
917 @vindex message-header-setup-hook
918 Hook called narrowed to the headers after initializing the headers.
920 @item message-send-hook
921 @vindex message-send-hook
922 Hook run before sending messages.
924 @item message-send-mail-hook
925 @vindex message-send-mail-hook
926 Hook run before sending mail messages.
928 @item message-send-news-hook
929 @vindex message-send-news-hook
930 Hook run before sending news messages.
932 @item message-sent-hook
933 @vindex message-sent-hook
934 Hook run after sending messages.
936 @item message-mode-syntax-table
937 @vindex message-mode-syntax-table
938 Syntax table used in message mode buffers.
944 @node Sending Variables
945 @section Sending Variables
949 @item message-fcc-handler-function
950 @vindex message-fcc-handler-function
951 A function called to save outgoing articles. This function will be
952 called with the name of the file to store the article in. The default
953 function is @code{rmail-output} which saves in Unix mailbox format.
955 @item message-courtesy-message
956 @vindex message-courtesy-message
957 When sending combined messages, this string is inserted at the start of
958 the mailed copy. If the string contains the format spec @samp{%s}, the
959 newsgroups the article has been posted to will be inserted there. If
960 this variable is @code{nil}, no such courtesy message will be added.
961 The default value is @samp{"The following message is a courtesy copy of
962 an article\nthat has been posted to %s as well.\n\n"}.
967 @node Message Buffers
968 @section Message Buffers
970 Message will generate new buffers with unique buffer names when you
971 request a message buffer. When you send the message, the buffer isn't
972 normally killed off. Its name is changed and a certain number of old
973 message buffers are kept alive.
976 @item message-generate-new-buffers
977 @vindex message-generate-new-buffers
978 If non-@code{nil}, generate new buffers. The default is @code{t}. If
979 this is a function, call that function with three parameters: The type,
980 the to address and the group name. (Any of these may be @code{nil}.)
981 The function should return the new buffer name.
983 @item message-max-buffers
984 @vindex message-max-buffers
985 This variable says how many old message buffers to keep. If there are
986 more message buffers than this, the oldest buffer will be killed. The
987 default is 10. If this variable is @code{nil}, no old message buffers
990 @item message-send-rename-function
991 @vindex message-send-rename-function
992 After sending a message, the buffer is renamed from, for instance,
993 @samp{*reply to Lars*} to @samp{*sent reply to Lars*}. If you don't
994 like this, set this variable to a function that renames the buffer in a
995 manner you like. If you don't want to rename the buffer at all, you can
999 (setq message-send-rename-function 'ignore)
1002 @item message-kill-buffer-on-exit
1003 @findex message-kill-buffer-on-exit
1004 If non-@code{nil}, kill the buffer immediately on exit.
1009 @node Message Actions
1010 @section Message Actions
1012 When Message is being used from a news/mail reader, the reader is likely
1013 to want to perform some task after the message has been sent. Perhaps
1014 return to the previous window configuration or mark an article as
1017 @vindex message-kill-actions
1018 @vindex message-postpone-actions
1019 @vindex message-exit-actions
1020 @vindex message-send-actions
1021 The user may exit from the message buffer in various ways. The most
1022 common is @kbd{C-c C-c}, which sends the message and exits. Other
1023 possibilities are @kbd{C-c C-s} which just sends the message, @kbd{C-c
1024 C-d} which postpones the message editing and buries the message buffer,
1025 and @kbd{C-c C-k} which kills the message buffer. Each of these actions
1026 have lists associated with them that contains actions to be executed:
1027 @code{message-send-actions}, @code{message-exit-actions},
1028 @code{message-postpone-actions}, and @code{message-kill-actions}.
1030 Message provides a function to interface with these lists:
1031 @code{message-add-action}. The first parameter is the action to be
1032 added, and the rest of the arguments are which lists to add this action
1033 to. Here's an example from Gnus:
1037 `(set-window-configuration ,(current-window-configuration))
1038 'exit 'postpone 'kill)
1041 This restores the Gnus window configuration when the message buffer is
1042 killed, postponed or exited.
1044 An @dfn{action} can be either: a normal function, or a list where the
1045 @code{car} is a function and the @code{cdr} is the list of arguments, or
1046 a form to be @code{eval}ed.