diff options
| author | Richard M. Stallman | 2006-02-08 00:16:21 +0000 |
|---|---|---|
| committer | Richard M. Stallman | 2006-02-08 00:16:21 +0000 |
| commit | 2b02353b7bfdf86d0c333b00896d7752a9f408e9 (patch) | |
| tree | dd7856a5394ba2d36fb6df3640cce145c606950b | |
| parent | f44aa2679561581c3a81eb40a70b01e1862d6b0b (diff) | |
| download | emacs-2b02353b7bfdf86d0c333b00896d7752a9f408e9.tar.gz emacs-2b02353b7bfdf86d0c333b00896d7752a9f408e9.zip | |
Minor clarifications.
| -rw-r--r-- | man/sending.texi | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/man/sending.texi b/man/sending.texi index 4670a98f467..2fbf9a189c7 100644 --- a/man/sending.texi +++ b/man/sending.texi | |||
| @@ -93,9 +93,10 @@ header fields, such as @samp{Date} and @samp{Sender}, are created | |||
| 93 | automatically when you send the message. Others, such as the recipient | 93 | automatically when you send the message. Others, such as the recipient |
| 94 | names, must be specified by you in order to send the message properly. | 94 | names, must be specified by you in order to send the message properly. |
| 95 | 95 | ||
| 96 | Mail mode provides a few commands to help you edit some header fields, | 96 | In the mail buffer, you can insert and edit header fields using |
| 97 | and some are preinitialized in the buffer automatically at times. You can | 97 | ordinary editing commands. Mail mode provides a commands to help you |
| 98 | insert and edit header fields using ordinary editing commands. | 98 | edit some header fields, and some are preinitialized in the buffer |
| 99 | automatically when appropriate. | ||
| 99 | 100 | ||
| 100 | The line in the buffer that says | 101 | The line in the buffer that says |
| 101 | 102 | ||
| @@ -110,7 +111,7 @@ headers precede it. The delimiter line itself does not appear in the | |||
| 110 | message actually sent. The text used for the delimiter line is controlled | 111 | message actually sent. The text used for the delimiter line is controlled |
| 111 | by the variable @code{mail-header-separator}. | 112 | by the variable @code{mail-header-separator}. |
| 112 | 113 | ||
| 113 | Here is an example of what the headers and text in the mail buffer | 114 | Here is an example of what the headers and text in the mail buffer |
| 114 | might look like. | 115 | might look like. |
| 115 | 116 | ||
| 116 | @example | 117 | @example |
| @@ -221,7 +222,7 @@ of places to send the message. These fields can also have | |||
| 221 | continuation lines: one or more lines starting with whitespace, | 222 | continuation lines: one or more lines starting with whitespace, |
| 222 | following the starting line of the field, are considered part of the | 223 | following the starting line of the field, are considered part of the |
| 223 | field. Here's an example of a @samp{To} field with a continuation | 224 | field. Here's an example of a @samp{To} field with a continuation |
| 224 | line:@refill | 225 | line: |
| 225 | 226 | ||
| 226 | @example | 227 | @example |
| 227 | @group | 228 | @group |
| @@ -433,9 +434,8 @@ lowest priority for reselection by default, since you are finished with | |||
| 433 | using it. This is the usual way to send the message. | 434 | using it. This is the usual way to send the message. |
| 434 | 435 | ||
| 435 | In a file-visiting buffer, sending the message does not clear the | 436 | In a file-visiting buffer, sending the message does not clear the |
| 436 | modified flag, because only saving the file should do that. As a | 437 | modified flag, because only saving the file should do that. Also, you |
| 437 | result, you don't get a warning if you try to send the same message | 438 | don't get a warning if you try to send the same message twice. |
| 438 | twice. | ||
| 439 | 439 | ||
| 440 | @c This is indexed in mule.texi, node "Recognize Coding". | 440 | @c This is indexed in mule.texi, node "Recognize Coding". |
| 441 | @c @vindex sendmail-coding-system | 441 | @c @vindex sendmail-coding-system |