Index: message.texi =================================================================== RCS file: /usr/local/cvsroot/gnus/texi/message.texi,v retrieving revision 6.57 diff -u -c -u -r6.57 message.texi cvs server: conflicting specifications of output style cvs server: conflicting specifications of output style --- message.texi 2003/01/06 03:02:21 6.57 +++ message.texi 2003/01/07 17:17:48 @@ -18,7 +18,8 @@ This file documents Message, the Emacs message composition mode. -Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc. +Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 +Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or @@ -437,17 +438,17 @@ other headers and set to the value of all addresses in To: and Cc: @kindex C-c C-f C-a -@findex message-gen-unsubscribed-mft +@findex message-generate-unsubscribed-mail-followup-to @kindex C-c C-f C-m @findex message-goto-mail-followup-to Hm. ``So'', you ask, ``what if I send an email to a list I am not -subscribed to? I want my MFT to say that I want an extra copy.'' -(This is supposed to be interpreted by others the same way as if there -were no MFT, but you can use an explicit MFT to override someone -else's to-address group parameter.) The function -@code{message-gen-unsubscribed-mft} might come in handy. It is bound -to @kbd{C-c C-f C-a} by default. In any case, you can insert a MFT of -your own choice; @kbd{C-c C-f C-m} +subscribed to? I want my MFT to say that I want an extra copy.'' (This +is supposed to be interpreted by others the same way as if there were no +MFT, but you can use an explicit MFT to override someone else's +to-address group parameter.) The function +@code{message-generate-unsubscribed-mail-followup-to} might come in +handy. It is bound to @kbd{C-c C-f C-a} by default. In any case, you +can insert a MFT of your own choice; @kbd{C-c C-f C-m} (@code{message-goto-mail-followup-to}) will help you get started. @c @node Honoring an MFT post @@ -480,7 +481,7 @@ @menu * Buffer Entry:: Commands after entering a Message buffer. -* Header Commands:: Commands for moving to headers. +* Header Commands:: Commands for moving headers or changing headers. * Movement:: Moving around in message buffers. * Insertion:: Inserting things into message buffers. * MIME:: @sc{mime} considerations. @@ -510,10 +511,11 @@ @node Header Commands @section Header Commands -All these commands move to the header in question (except for the -@samp{Importance:} related commands). If it doesn't exist, it will be -inserted. +@subsection Commands for moving to headers +These following commands move to the header in question. If it doesn't +exist, it will be inserted. + @table @kbd @item C-c ? @@ -591,17 +593,117 @@ buffer, it cycles between the three valid values according to RFC 1376: @samp{low}, @samp{normal} and @samp{high}. +@item C-c C-f C-a +@kindex C-c C-f C-a +@findex message-generate-unsubscribed-mail-followup-to +Insert a reasonable @samp{Mail-Followup-To:} header +(@pxref{Mailing Lists}) in a post to an +unsubscribed list. When making original posts to a mailing list you are +not subscribed to, you have to type in a @samp{Mail-Followup-To:} header +by hand. The contents, usually, are the addresses of the list and your +own address. This function inserts such a header automatically. It +fetches the contents of the @samp{To:} header in the current mail +buffer, and appends the current @code{user-mail-address}. + +If the optional argument @code{include-cc} is non-nil, the addresses in +the @samp{Cc:} header are also put into the @samp{Mail-Followup-To:} +header. + +@end table + +@subsection Commands to change headers + +@table @kbd + +@item C-c C-o +@kindex C-c C-o +@findex message-sort-headers +@vindex message-header-format-alist +Sort headers according to @code{message-header-format-alist} +(@code{message-sort-headers}). + +@item C-c C-t +@kindex C-c C-t +@findex message-insert-to +Insert a @code{To} header that contains the @code{Reply-To} or +@code{From} header of the message you're following up +(@code{message-insert-to}). + +@item C-c C-n +@kindex C-c C-n +@findex message-insert-newsgroups +Insert a @code{Newsgroups} header that reflects the @code{Followup-To} +or @code{Newsgroups} header of the article you're replying to +(@code{message-insert-newsgroups}). + +@item C-c C-l +@kindex C-c C-l +@findex message-to-list-only +Send a message to the list only. Remove all addresses but the list +address from @code{To:} and @code{Cc:} headers. + +@item C-c M-n +@kindex C-c M-n +@findex message-insert-disposition-notification-to +Insert a request for a disposition +notification. (@code{message-insert-disposition-notification-to}). +This means that if the recipient support RFC 2298 she might send you a +notification that she received the message. + @item M-x message-insert-importance-high @kindex M-x message-insert-importance-high @findex message-insert-importance-high -Insert a @samp{Importance:} header with a value of @samp{high}, +@cindex Importance +Insert an @samp{Importance:} header with a value of @samp{high}, deleting headers if necessary. @item M-x message-insert-importance-low @kindex M-x message-insert-importance-low @findex message-insert-importance-low -Insert a @samp{Importance:} header with a value of @samp{low}, -deleting headers if necessary. +@cindex Importance +Insert an @samp{Importance:} header with a value of @samp{low}, deleting +headers if necessary. + +@item C-c C-f s +@kindex C-c C-f s +@findex message-change-subject +@cindex Subject +Change the current @samp{Subject:} header. Ask for new @samp{Subject:} +header and append @code{(was: )}. The old subject can be +stripped on replying, see @code{message-subject-trailing-was-query} +(@pxref{Message Headers}). + +@item C-c C-f x +@kindex C-c C-f x +@findex message-cross-post-followup-to +@vindex message-cross-post-default +@cindex X-Post +@cindex cross-post +Ask for an additional @samp{Newsgroups:} and @samp{FollowUp-To:} for a +cross-post. @code{message-cross-post-followup-to} mangles +@samp{FollowUp-To:} and @samp{Newsgroups:} header to point to group. +If @code{message-cross-post-default} is @code{nil} or if called with a +prefix-argument @samp{Follow-Up:} is set, but the message is not +cross-posted. + +@item C-c C-f t +@kindex C-c C-f t +@findex message-reduce-to-to-cc +Replace contents of @samp{To:} header with contents of @samp{Cc:} or +@samp{Bcc:} header. + +@item C-c C-f a +@kindex C-c C-f a +@findex message-add-archive-header +@vindex message-archive-header +@vindex message-archive-note +@cindex X-No-Archive +Insert @samp{X-No-Archive: Yes} in the header and a note in the body. +The header and the note can be customized using +@code{message-archive-header} and @code{message-archive-note}. When +called with a prefix argument, ask for a text to insert. If you don't +want the note in the body, set @code{message-archive-note} to +@code{nil}. @end table @@ -670,13 +772,17 @@ @findex message-insert-headers Insert the message headers (@code{message-insert-headers}). -@item C-c M-n -@kindex C-c M-n -@findex message-insert-disposition-notification-to -Insert a request for a disposition -notification. (@code{message-insert-disposition-notification-to}). -This means that if the recipient support RFC 2298 she might send you a -notification that she received the message. +@item C-c M-m +@kindex C-c M-m +@findex message-mark-inserted-region +Mark some region in the current article with enclosing tags. +See @code{message-mark-insert-begin} and @code{message-mark-insert-end}. + +@item C-c M-f +@kindex C-c M-f +@findex message-mark-insert-file +Insert a file in the current article with enclosing tags. +See @code{message-mark-insert-begin} and @code{message-mark-insert-end}. @end table @@ -944,36 +1050,6 @@ @samp{*} says where point will be placed. -@item C-c C-t -@kindex C-c C-t -@findex message-insert-to -Insert a @code{To} header that contains the @code{Reply-To} or -@code{From} header of the message you're following up -(@code{message-insert-to}). - -@item C-c M-t -@kindex C-c M-t -@findex message-insert-wide-reply -Insert @code{To} and @code{Cc} headers that contains addresses as if -you were doing a wide reply to the original message -(@code{message-insert-wide-reply}). This usually means that all -addresses from @code{To}, @code{From}/@code{Reply-To}, and @code{Cc} -will be picked up. - -@item C-c C-n -@kindex C-c C-n -@findex message-insert-newsgroups -Insert a @code{Newsgroups} header that reflects the @code{Followup-To} -or @code{Newsgroups} header of the article you're replying to -(@code{message-insert-newsgroups}). - -@item C-c C-o -@kindex C-c C-o -@findex message-sort-headers -@vindex message-header-format-alist -Sort headers according to @code{message-header-format-alist} -(@code{message-sort-headers}). - @item C-c M-r @kindex C-c M-r @findex message-rename-buffer @@ -1208,6 +1284,18 @@ "^\\(\\(\\([Rr][Ee]\\|[Ss][Vv]\\|[Aa][Ww]\\): *\\)+\\)") @end lisp +@item message-subject-trailing-was-query +@vindex message-subject-trailing-was-query +@vindex message-subject-trailing-was-ask-regexp +@vindex message-subject-trailing-was-regexp +Controls what to do with trailing @samp{(was: )} in subject +lines. If @code{nil}, leave the subject unchanged. If it is the symbol +@code{ask}, query the user what do do. In this case, the subject is +matched against @code{message-subject-trailing-was-ask-regexp}. If +@code{message-subject-trailing-was-query} is t, always strip the +trailing old subject. In this case, +@code{message-subject-trailing-was-regexp} is used. + @item message-alternative-emails @vindex message-alternative-emails A regexp to match the alternative email addresses. The first matched @@ -1600,6 +1688,14 @@ This can also be a list of functions. Each function can find the citation between @code{(point)} and @code{(mark t)}. And each function should leave point and mark around the citation text as modified. + +@item message-mark-insert-begin +@vindex message-mark-insert-begin +String to mark the beginning of some inserted text. + +@item message-mark-insert-end +@vindex message-mark-insert-end +String to mark the end of some inserted text. @item message-signature @vindex message-signature