mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2024-11-23 07:19:15 +00:00
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)
This commit is contained in:
parent
845fe038e7
commit
0d8bae5c55
@ -82,7 +82,7 @@ hear the lamentation of their women.
|
||||
At the top of the mail buffer is a set of @dfn{header fields}, which
|
||||
are used for specifying information about the email's recipient(s),
|
||||
subject, and so on. The above buffer contains header fields for
|
||||
@samp{To}, @samp{Cc}, @samp{Subject}, and @samp{From}. Some header
|
||||
@samp{To}, @samp{CC}, @samp{Subject}, and @samp{From}. Some header
|
||||
fields are automatically pre-initialized in the mail buffer, when
|
||||
appropriate.
|
||||
|
||||
@ -152,23 +152,23 @@ more than one address, use commas to separate them.
|
||||
@item Subject
|
||||
The subject of the message.
|
||||
|
||||
@item Cc
|
||||
@item CC
|
||||
Additional mailing address(es) to send the message to. This is like
|
||||
@samp{To}, except that these readers should not regard the message as
|
||||
directed at them.
|
||||
|
||||
@item Bcc
|
||||
@item BCC
|
||||
Additional mailing address(es) to send the message to, which should
|
||||
not appear in the header of the message actually sent. @samp{Bcc} stands
|
||||
not appear in the header of the message actually sent. @samp{BCC} stands
|
||||
for @dfn{blind carbon copies}.
|
||||
|
||||
@item Fcc
|
||||
@item FCC
|
||||
The name of a file, to which a copy of the sent message should be
|
||||
appended. Emacs writes the message in mbox format, unless the file is
|
||||
in Babyl format (used by Rmail before Emacs 23), in which case Emacs
|
||||
writes in Babyl format. If an Rmail buffer is visiting the file,
|
||||
Emacs updates it accordingly. To specify more than one file, use
|
||||
several @samp{Fcc} fields, with one file name in each field.
|
||||
several @samp{FCC} fields, with one file name in each field.
|
||||
|
||||
@item Reply-to
|
||||
An address to which replies should be sent, instead of @samp{From}.
|
||||
@ -198,7 +198,7 @@ this is normally filled in automatically for you.
|
||||
@end table
|
||||
|
||||
@noindent
|
||||
The @samp{To}, @samp{Cc}, and @samp{Bcc} fields can appear any number
|
||||
The @samp{To}, @samp{CC}, and @samp{BCC} fields can appear any number
|
||||
of times, and each such header field can contain multiple addresses,
|
||||
separated by commas. This way, you can specify any number of places
|
||||
to send the message. These fields can also have continuation lines:
|
||||
@ -221,11 +221,11 @@ To: foo@@example.net, this@@example.net,
|
||||
buffer by setting the variable @code{mail-default-headers} to a
|
||||
string. Then @kbd{C-x m} inserts this string into the message
|
||||
headers. For example, here is how to add a @samp{Reply-to} and
|
||||
@samp{Fcc} header to each message:
|
||||
@samp{FCC} header to each message:
|
||||
|
||||
@smallexample
|
||||
(setq mail-default-headers
|
||||
"Reply-to: foo@@example.com\nFcc: ~/Mail/sent")
|
||||
"Reply-to: foo@@example.com\nFCC: ~/Mail/sent")
|
||||
@end smallexample
|
||||
|
||||
@noindent
|
||||
@ -293,7 +293,7 @@ alias definitions and include commands.
|
||||
Mail aliases expand as abbrevs---that is to say, as soon as you type
|
||||
a word-separator character after an alias (@pxref{Abbrevs}). This
|
||||
expansion takes place only within the @samp{To}, @samp{From},
|
||||
@samp{Cc}, @samp{Bcc}, and @samp{Reply-to} header fields (plus their
|
||||
@samp{CC}, @samp{BCC}, and @samp{Reply-to} header fields (plus their
|
||||
@samp{Resent-} variants); it does not take place in other header
|
||||
fields, such as @samp{Subject}.
|
||||
|
||||
@ -418,16 +418,16 @@ Move to the @samp{To} header (@code{message-goto-to}).
|
||||
@item C-c C-f C-s
|
||||
Move to the @samp{Subject} header (@code{message-goto-subject}).
|
||||
@item C-c C-f C-c
|
||||
Move to the @samp{Cc} header (@code{message-goto-cc}).
|
||||
Move to the @samp{CC} header (@code{message-goto-cc}).
|
||||
@item C-c C-f C-b
|
||||
Move to the @samp{Bcc} header (@code{message-goto-bcc}).
|
||||
Move to the @samp{BCC} header (@code{message-goto-bcc}).
|
||||
@item C-c C-f C-r
|
||||
Move to the @samp{Reply-to} header (@code{message-goto-reply-to}).
|
||||
@item C-c C-f C-f
|
||||
Move to the @samp{Mail-Followup-To} header field
|
||||
(@code{message-goto-followup-to}).
|
||||
@item C-c C-f C-w
|
||||
Add a new @samp{Fcc} header field, with file-name completion
|
||||
Add a new @samp{FCC} header field, with file-name completion
|
||||
(@code{message-goto-fcc}).
|
||||
@item C-c C-b
|
||||
Move to the start of the message body (@code{message-goto-body}).
|
||||
@ -463,7 +463,7 @@ the body.
|
||||
@findex message-tab
|
||||
@kindex TAB @r{(Message mode)}
|
||||
While editing a header field that contains addresses, such as
|
||||
@samp{To:}, @samp{Cc:} and @samp{Bcc:}, you can complete an address by
|
||||
@samp{To:}, @samp{CC:} and @samp{BCC:}, you can complete an address by
|
||||
typing @key{TAB} (@code{message-tab}). This attempts to insert the
|
||||
full name corresponding to the address based on a couple of methods,
|
||||
including EUDC, a library that recognizes a number of directory server
|
||||
|
Loading…
Reference in New Issue
Block a user