xemacs-beta: man/message.texi comparison

comparison man/message.texi @ 16:0293115a14e9 r19-15b91

Import from CVS: tag r19-15b91

author	cvs
date	Mon, 13 Aug 2007 08:49:20 +0200
parents	376386a54a3c
children	4103f0995bd7

comparison

equal deleted inserted replaced

-:ad457d5f7d04
+:0293115a14e9
 \input texinfo                  @c -*-texinfo-*-
-@setfilename ../info/message.info
+@setfilename message
 @settitle Message Manual
 @synindex fn cp
 @synindex vr cp
 @synindex pg cp
 @iftex
 @node Wide Reply
 @section Wide Reply
 @findex message-wide-reply
 The @code{message-wide-reply} pops up a message buffer that's a wide
-reply to the message in the current buffer.
+reply to the message in the current buffer.  A @dfn{wide reply} is a
+reply that goes out to all people listed in the @code{To}, @code{From}
+and @code{Cc} headers.
 @vindex message-wide-reply-to-function
 Message uses the normal methods to determine where wide replies are to go,
 but you can change the behavior to suit your needs by fiddling with the
 @code{message-wide-reply-to-function}.  It is used in the same way as
 @code{message-reply-to-function} (@pxref{Reply}).
 @findex rmail-dont-reply-to-names
-Addresses that matches the @code{rmail-dont-reply-to-names} regular
+Addresses that match the @code{rmail-dont-reply-to-names} regular
 expression will be removed from the @code{Cc} header.
 @node Followup
 @section Followup
 The @code{message-supersede} command pops up a message buffer that will
 supersede the message in the current buffer.
 @vindex message-ignored-supersedes-headers
 Headers matching the @code{message-ignored-supersedes-headers} are
-removed before popping up the new message buffer.  The default is
+removed before popping up the new message buffer.  The default is@*
-@samp{^Path:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|^Received:\\|^X-From-Line:\\|Return-Path:}.
+@samp{^Path:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|@*
+^Received:\\|^X-From-Line:\\|Return-Path:}.
 @node Forwarding
 @section Forwarding
 news.
 @table @code
 @item message-forward-start-separator
 @vindex message-forward-start-separator
-Delimiter inserted before forwarded messages.  The default is
+Delimiter inserted before forwarded messages.  The default is@*
 @samp{------- Start of forwarded message -------\n}.
 @vindex message-forward-end-separator
 @item message-forward-end-separator
 @vindex message-forward-end-separator
-Delimiter inserted after forwarded messages.  The default is
+Delimiter inserted after forwarded messages.  The default is@*
 @samp{------- End of forwarded message -------\n}.
 @item message-signature-before-forwarded-message
 @vindex message-signature-before-forwarded-message
 If this variable is @code{t}, which it is by default, your personal
 @findex message-resend
 The @code{message-resend} command will prompt the user for an address
 and resend the message in the current buffer to that address.
 @vindex message-ignored-resent-headers
-Headers the match the @code{message-ignored-resent-headers} regexp will
+Headers that match the @code{message-ignored-resent-headers} regexp will
 be removed before sending the message.  The default is
 @samp{^Return-receipt}.
 @node Bouncing
 @section Bouncing
 @findex message-bounce
 The @code{message-bounce} command will, if the current buffer contains a
 bounced mail message, pop up a message buffer stripped of the bounce
-information.
+information.  A @dfn{bounced message} is typically a mail you've sent
+out that has been returned by some @code{mailer-daemon} as
+undeliverable.
 @vindex message-ignored-bounced-headers
 Headers that match the @code{message-ignored-bounced-headers} regexp
 will be removed before popping up the buffer.  The default is
 @samp{^Received:}.
 Note that RFC1036 says that a signature should be preceded by the three
 characters @samp{-- } on a line by themselves.  This is to make it
 easier for the recipient to automatically recognize and process the
 signature.  So don't remove those characters, even though you might feel
-that they ruin you beautiful design, like, totally.
+that they ruin your beautiful design, like, totally.
 Also note that no signature should be more than four lines long.
 Including ASCII graphics is an efficient way to get everybody to believe
 that you are silly and have nothing important to say.
 @findex message-caesar-buffer-body
 Caesar rotate (aka. rot13) the current message
 (@code{message-caesar-buffer-body}).  If narrowing is in effect, just
 rotate the visible portion of the buffer.  A numerical prefix says how
 many places to rotate the text.  The default is 13.
+@item C-c C-e
+@kindex C-c C-e
+@findex message-elide-region
+Elide the text between point and mark (@code{message-elide-region}).
+The text is killed and an ellipsis (@samp{[...]}) will be inserted in
+its place.
 @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
 @section Mail Headers
 @table @code
 @item message-required-mail-headers
 @vindex message-required-mail-headers
-See @pxref{News Headers} for the syntax of this variable.  It is
+@xref{News Headers}, for the syntax of this variable.  It is
 @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines
 (optional . X-Mailer))} by default.
 @item message-ignored-mail-headers
 @vindex message-ignored-mail-headers
 @cindex Message-ID
 @vindex mail-host-address
 @findex system-name
 @cindex Sun
 This required header will be generated by Message.  A unique ID will be
-created based on date, time, user name and system name.  Message will
+created based on the date, time, user name and system name.  Message will
 use @code{mail-host-address} as the fully qualified domain name (FQDN)
-of the machine if that variable is define.  If not, it will use
+of the machine if that variable is defined.  If not, it will use
 @code{system-name}, which doesn't report a FQDN on some machines --
 notably Suns.
 @item X-Newsreader
 @cindex X-Newsreader
 @code{message-mailer} local variable, unless there already is an
 @code{X-Newsreader} header present.
 @item In-Reply-To
 This optional header is filled out using the @code{Date} and @code{From}
-header of the article being replied.
+header of the article being replied to.
 @item Expires
 @cindex Expires
 This extremely optional header will be inserted according to the
 @code{message-expires} variable.  It is highly deprecated and shouldn't
 @code{message-distribution-function} variable.  It is a deprecated and
 much misunderstood header.
 @item Path
 @cindex path
-This extremely optional header should probably not ever be used.
+This extremely optional header should probably never be used.
 However, some @emph{very} old servers require that this header is
 present.  @code{message-user-path} further controls how this
-@code{Path} header is to look.  If is is @code{nil}, the the server name
+@code{Path} header is to look.  If it is @code{nil}, use the server name
-as the leaf node.  If is is a string, use the string.  If it is neither
+as the leaf node.  If it is a string, use the string.  If it is neither
 a string nor @code{nil}, use the user name only.  However, it is highly
 unlikely that you should need to fiddle with this variable at all.
 @end table
 @findex yow
 @table @code
 @item message-syntax-checks
 @vindex message-syntax-checks
-If non-@code{nil}, message will attempt to check the legality of the
+If non-@code{nil}, Message will attempt to check the legality of the
 headers, as well as some other stuff, before posting.  You can control
 the granularity of the check by adding or removing elements from this
 list.  Legal elements are:
 @table @code
 @item empty
 Check whether the article is empty.
 @item empty-headers
 Check whether any of the headers are empty.
 @item existing-newsgroups
-Check whether the newsgroups mentioned in the Newsgroups and
+Check whether the newsgroups mentioned in the @code{Newsgroups} and
-Followup-To headers exist.
+@code{Followup-To} headers exist.
 @item valid-newsgroups
-Check whether the @code{Newsgroups} and @code{Followup-To} headers
+Check whether the @code{Newsgroups} and @code{Followup-to} headers
-are valid syntactially.
+are valid syntactically.
+@item shorten-followup-to
+Check whether to add a @code{Followup-to} header to shorten the number
+of groups to post to.
 @end table
 All these conditions are checked by default.
 @item message-ignored-news-headers
 @vindex message-ignored-news-headers
-Regexp of headers to be removed before posting.  The default is
+Regexp of headers to be removed before posting.  The default is@*
 @samp{^NNTP-Posting-Host:\\|^Xref:\\|^Bcc:\\|^Gcc:\\|^Fcc:}.
 @item message-default-news-headers
 @vindex message-default-news-headers
 This string is inserted at the end of the headers in all message
 buffers that are initialized as news.
 Hook called narrowed to the headers after initializing the headers.
 @item message-send-hook
 @vindex message-send-hook
 Hook run before sending messages.
+@item message-send-mail-hook
+@vindex message-send-mail-hook
+Hook run before sending mail messages.
+@item message-send-news-hook
+@vindex message-send-news-hook
+Hook run before sending news messages.
 @item message-sent-hook
 @vindex message-sent-hook
 Hook run after sending messages.
 function is @code{rmail-output} which saves in Unix mailbox format.
 @item message-courtesy-message
 @vindex message-courtesy-message
 When sending combined messages, this string is inserted at the start of
-the mailed copy.  If this variable is @code{nil}, no such courtesy
+the mailed copy.  If the string contains the format spec @samp{%s}, the
-message will be added.
+newsgroups the article has been posted to will be inserted there.  If
+this variable is @code{nil}, no such courtesy message will be added.
+The default value is @samp{"The following message is a courtesy copy of
+an article\nthat has been posted to %s as well.\n\n"}.
 @end table
 @node Message Buffers
 @section Message Buffers
 Message will generate new buffers with unique buffer names when you
 request a message buffer.  When you send the message, the buffer isn't
-normally killed off.  It's name is changed and a certain number of old
+normally killed off.  Its name is changed and a certain number of old
 message buffers are kept alive.
 @table @code
 @item message-generate-new-buffers
 @vindex message-generate-new-buffers
 @end lisp
 This restores the Gnus window configuration when the message buffer is
 killed, postponed or exited.
-An @dfn{action} can be either a normal function; or a list where the
+An @dfn{action} can be either: a normal function, or a list where the
-@code{car} is a function and the @code{cdr} is the list of arguments; or
+@code{car} is a function and the @code{cdr} is the list of arguments, or
 a form to be @code{eval}ed.
 @node Index
 @chapter Index
 @printindex cp

Mercurial > hg > xemacs-beta

comparison man/message.texi @ 16:0293115a14e9 r19-15b91