aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEli Zaretskii2018-05-20 12:08:03 +0300
committerEli Zaretskii2018-05-20 12:08:03 +0300
commit0d8bae5c5543e67aebc773a114aedb2f215aba73 (patch)
treea55d51c2d963a982baa6b5ce8cb6ca37def4f934
parent845fe038e790c7c62c6b294f88648644a4ae7ddd (diff)
downloademacs-0d8bae5c5543e67aebc773a114aedb2f215aba73.tar.gz
emacs-0d8bae5c5543e67aebc773a114aedb2f215aba73.zip
Fix capitalization of mail headers
* doc/emacs/sending.texi (Mail Format, Mail Headers) (Mail Aliases, Header Editing): Use consistent capitalization of CC, BCC, and FCC. (Bug#31532)
-rw-r--r--doc/emacs/sending.texi28
1 files changed, 14 insertions, 14 deletions
diff --git a/doc/emacs/sending.texi b/doc/emacs/sending.texi
index b7bdd69c7c2..0c5caf0ff98 100644
--- a/doc/emacs/sending.texi
+++ b/doc/emacs/sending.texi
@@ -82,7 +82,7 @@ hear the lamentation of their women.
82At the top of the mail buffer is a set of @dfn{header fields}, which 82At the top of the mail buffer is a set of @dfn{header fields}, which
83are used for specifying information about the email's recipient(s), 83are used for specifying information about the email's recipient(s),
84subject, and so on. The above buffer contains header fields for 84subject, and so on. The above buffer contains header fields for
85@samp{To}, @samp{Cc}, @samp{Subject}, and @samp{From}. Some header 85@samp{To}, @samp{CC}, @samp{Subject}, and @samp{From}. Some header
86fields are automatically pre-initialized in the mail buffer, when 86fields are automatically pre-initialized in the mail buffer, when
87appropriate. 87appropriate.
88 88
@@ -152,23 +152,23 @@ more than one address, use commas to separate them.
152@item Subject 152@item Subject
153The subject of the message. 153The subject of the message.
154 154
155@item Cc 155@item CC
156Additional mailing address(es) to send the message to. This is like 156Additional mailing address(es) to send the message to. This is like
157@samp{To}, except that these readers should not regard the message as 157@samp{To}, except that these readers should not regard the message as
158directed at them. 158directed at them.
159 159
160@item Bcc 160@item BCC
161Additional mailing address(es) to send the message to, which should 161Additional mailing address(es) to send the message to, which should
162not appear in the header of the message actually sent. @samp{Bcc} stands 162not appear in the header of the message actually sent. @samp{BCC} stands
163for @dfn{blind carbon copies}. 163for @dfn{blind carbon copies}.
164 164
165@item Fcc 165@item FCC
166The name of a file, to which a copy of the sent message should be 166The name of a file, to which a copy of the sent message should be
167appended. Emacs writes the message in mbox format, unless the file is 167appended. Emacs writes the message in mbox format, unless the file is
168in Babyl format (used by Rmail before Emacs 23), in which case Emacs 168in Babyl format (used by Rmail before Emacs 23), in which case Emacs
169writes in Babyl format. If an Rmail buffer is visiting the file, 169writes in Babyl format. If an Rmail buffer is visiting the file,
170Emacs updates it accordingly. To specify more than one file, use 170Emacs updates it accordingly. To specify more than one file, use
171several @samp{Fcc} fields, with one file name in each field. 171several @samp{FCC} fields, with one file name in each field.
172 172
173@item Reply-to 173@item Reply-to
174An address to which replies should be sent, instead of @samp{From}. 174An address to which replies should be sent, instead of @samp{From}.
@@ -198,7 +198,7 @@ this is normally filled in automatically for you.
198@end table 198@end table
199 199
200@noindent 200@noindent
201The @samp{To}, @samp{Cc}, and @samp{Bcc} fields can appear any number 201The @samp{To}, @samp{CC}, and @samp{BCC} fields can appear any number
202of times, and each such header field can contain multiple addresses, 202of times, and each such header field can contain multiple addresses,
203separated by commas. This way, you can specify any number of places 203separated by commas. This way, you can specify any number of places
204to send the message. These fields can also have continuation lines: 204to send the message. These fields can also have continuation lines:
@@ -221,11 +221,11 @@ To: foo@@example.net, this@@example.net,
221buffer by setting the variable @code{mail-default-headers} to a 221buffer by setting the variable @code{mail-default-headers} to a
222string. Then @kbd{C-x m} inserts this string into the message 222string. Then @kbd{C-x m} inserts this string into the message
223headers. For example, here is how to add a @samp{Reply-to} and 223headers. For example, here is how to add a @samp{Reply-to} and
224@samp{Fcc} header to each message: 224@samp{FCC} header to each message:
225 225
226@smallexample 226@smallexample
227(setq mail-default-headers 227(setq mail-default-headers
228 "Reply-to: foo@@example.com\nFcc: ~/Mail/sent") 228 "Reply-to: foo@@example.com\nFCC: ~/Mail/sent")
229@end smallexample 229@end smallexample
230 230
231@noindent 231@noindent
@@ -293,7 +293,7 @@ alias definitions and include commands.
293 Mail aliases expand as abbrevs---that is to say, as soon as you type 293 Mail aliases expand as abbrevs---that is to say, as soon as you type
294a word-separator character after an alias (@pxref{Abbrevs}). This 294a word-separator character after an alias (@pxref{Abbrevs}). This
295expansion takes place only within the @samp{To}, @samp{From}, 295expansion takes place only within the @samp{To}, @samp{From},
296@samp{Cc}, @samp{Bcc}, and @samp{Reply-to} header fields (plus their 296@samp{CC}, @samp{BCC}, and @samp{Reply-to} header fields (plus their
297@samp{Resent-} variants); it does not take place in other header 297@samp{Resent-} variants); it does not take place in other header
298fields, such as @samp{Subject}. 298fields, such as @samp{Subject}.
299 299
@@ -418,16 +418,16 @@ Move to the @samp{To} header (@code{message-goto-to}).
418@item C-c C-f C-s 418@item C-c C-f C-s
419Move to the @samp{Subject} header (@code{message-goto-subject}). 419Move to the @samp{Subject} header (@code{message-goto-subject}).
420@item C-c C-f C-c 420@item C-c C-f C-c
421Move to the @samp{Cc} header (@code{message-goto-cc}). 421Move to the @samp{CC} header (@code{message-goto-cc}).
422@item C-c C-f C-b 422@item C-c C-f C-b
423Move to the @samp{Bcc} header (@code{message-goto-bcc}). 423Move to the @samp{BCC} header (@code{message-goto-bcc}).
424@item C-c C-f C-r 424@item C-c C-f C-r
425Move to the @samp{Reply-to} header (@code{message-goto-reply-to}). 425Move to the @samp{Reply-to} header (@code{message-goto-reply-to}).
426@item C-c C-f C-f 426@item C-c C-f C-f
427Move to the @samp{Mail-Followup-To} header field 427Move to the @samp{Mail-Followup-To} header field
428(@code{message-goto-followup-to}). 428(@code{message-goto-followup-to}).
429@item C-c C-f C-w 429@item C-c C-f C-w
430Add a new @samp{Fcc} header field, with file-name completion 430Add a new @samp{FCC} header field, with file-name completion
431(@code{message-goto-fcc}). 431(@code{message-goto-fcc}).
432@item C-c C-b 432@item C-c C-b
433Move to the start of the message body (@code{message-goto-body}). 433Move to the start of the message body (@code{message-goto-body}).
@@ -463,7 +463,7 @@ the body.
463@findex message-tab 463@findex message-tab
464@kindex TAB @r{(Message mode)} 464@kindex TAB @r{(Message mode)}
465 While editing a header field that contains addresses, such as 465 While editing a header field that contains addresses, such as
466@samp{To:}, @samp{Cc:} and @samp{Bcc:}, you can complete an address by 466@samp{To:}, @samp{CC:} and @samp{BCC:}, you can complete an address by
467typing @key{TAB} (@code{message-tab}). This attempts to insert the 467typing @key{TAB} (@code{message-tab}). This attempts to insert the
468full name corresponding to the address based on a couple of methods, 468full name corresponding to the address based on a couple of methods,
469including EUDC, a library that recognizes a number of directory server 469including EUDC, a library that recognizes a number of directory server