All these commands move to the header in question. If it doesn't exist, it will be inserted.
To
header (message-goto-to
).
Bcc
header (message-goto-bcc
).
Fcc
header (message-goto-fcc
).
Cc
header (message-goto-cc
).
Subject
header (message-goto-subject
).
Reply-To
header (message-goto-reply-to
).
Newsgroups
header (message-goto-newsgroups
).
Distribution
header (message-goto-distribution
).
Followup-To
header (message-goto-followup-to
).
Keywords
header (message-goto-keywords
).
Summary
header (message-goto-summary
).
message-goto-body
).
message-goto-signature
).
message-yank-original
).
message-fill-yanked-message
).
message-insert-signature
).
message-ignored-cited-headers
message-citation-line-function
message-insert-citation-line
.
message-yank-prefix
message-yank-prefix
prepended to it. The default is `> '.
If it is nil
, just indent the message.
message-indentation-spaces
message-cite-function
message-cite-original
. You can also set it to
sc-cite-original
to use Supercite.
message-indent-citation-function
(point)
and (mark t)
. And each function
should leave point and mark around the citation text as modified.
message-signature
t
(which is the default), the message-signature-file
file will be
inserted instead. If a function, the result from the function will be
used instead. If a form, the result from the form will be used instead.
If this variable is nil
, no signature will be inserted at all.
message-signature-file
Note that RFC1036 says that a signature should be preceded by the three characters `-- ' 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 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.
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.
message-elide-region
).
The text is killed and an ellipsis (`[...]') will be inserted in
its place.
To
header that contains the Reply-To
or
From
header of the message you're following up
(message-insert-to
).
Newsgroups
header that reflects the Followup-To
or Newsgroups
header of the article you're replying to
(message-insert-newsgroups
).
message-rename-buffer
). If given a prefix,
prompt for a new buffer name.
message-send-and-exit
).
message-send
).
message-dont-send
).
message-kill-buffer
).
Message uses mailabbrev
to handle mail aliases.
mailabbrev
works by parsing the `/etc/mailrc' and
`~/.mailrc' files. These files look like:
alias lmi "Lars Magne Ingebrigtsen <larsi@ifi.uio.no>" alias ding "ding@ifi.uio.no (ding mailing list)"
After adding lines like this to your `~/.mailrc' file, you should
be able to just write `lmi' in the To
or Cc
(and so
on) headers and press SPC to expand the alias.
No expansion will be performed upon sending of the message--all expansions have to be done explicitly.
Go to the first, previous, next, last section, table of contents.