If nil, the prepped message will be shown, for confirmation or
otherwise, in some window in the current frame without resizing
anything. That may or may not display enough of the message to
-distinguish it from others. If set to the symbol ‘queued’, take
+distinguish it from others. If set to the symbol `queued', take
this action only when running the queue. If set to the symbol
-‘immediate’, take this action only when sending immediately. For
+`immediate', take this action only when sending immediately. For
any other non-nil value, take the action in both cases. Even if
you're not confirming the sending of immediate or queued messages,
it can still be interesting to see a lot about them as they are
If a positive number, it's a timeout before sending. If a negative
number, it's a timeout before not sending. This will not work if your
version of Emacs doesn't include the function `y-or-n-p-with-timeout'
-\(e.g., some versions of XEmacs\)."
+\(e.g., some versions of XEmacs)."
:version "24.1"
:group 'feedmail-misc
:type '(choice (const nil) integer)
"If non-nil remove Bcc: lines from the message headers.
In any case, the Bcc: lines do participate in the composed address
list. You may want to leave them in if you're using sendmail
-\(see `feedmail-buffer-eating-function'\)."
+\(see `feedmail-buffer-eating-function')."
:group 'feedmail-headers
:type 'boolean
)
"If non-nil remove Resent-Bcc: lines from the message headers.
In any case, the Resent-Bcc: lines do participate in the composed
address list. You may want to leave them in if you're using sendmail
-\(see `feedmail-buffer-eating-function'\)."
+\(see `feedmail-buffer-eating-function')."
:group 'feedmail-headers
:type 'boolean
)
appropriate address headers in the message. Generally, they will show
up in the list of deduced addresses in the order that the headers
happen to appear (duplicate addresses are eliminated in any case).
-This variable can be set to the symbol ‘first’, in which case the
+This variable can be set to the symbol `first', in which case the
Bcc:/Resent-Bcc: addresses will appear at the beginning in the list;
-or, it can be set to the symbol ‘last’, in which case they will appear
+or, it can be set to the symbol `last', in which case they will appear
at the end of the list.
Why should you care? Well, maybe you don't, and certainly the same
seeing the message again. Some configurations of sendmail, for example,
seem to try to deliver to each addressee at least once, immediately
and serially, so slow SMTP conversations can add up to a delay. There
-is an option for either ‘first’ or ‘last’ because you might have a
+is an option for either `first' or `last' because you might have a
delivery agent that processes the addresses backwards."
:group 'feedmail-headers
:type '(choice (const nil)
"If non-nil and the email has no Sender: header, use this value.
May be nil, in which case nothing in particular is done with respect
to Sender: lines. By design, will not replace an existing Sender:
-line, but you can achieve that with a fiddle-plex 'replace action.
+line, but you can achieve that with a fiddle-plex replace action.
NB: it makes no sense to use the value t since there is no sensible
default for Sender:.
May be t, in which case a default is computed (and you probably won't
be happy with it). May be nil, in which case nothing in particular is
done with respect to From: lines. By design, will not replace an
-existing From: line, but you can achieve that with a fiddle-plex 'replace
+existing From: line, but you can achieve that with a fiddle-plex `replace'
action.
If neither nil nor t, it may be a string, a fiddle-plex, or a function
sendmail installations, one can mostly only wish it were otherwise. If feedmail
believes the sendmail program will sell you out this way, it won't use the \"-f\"
option when calling sendmail. If it doesn't think sendmail will sell you out,
-it will use the \"-f\" \(since it is a handy feature\). You control what
+it will use the \"-f\" \(since it is a handy feature). You control what
feedmail thinks with this variable. The default is nil, meaning that feedmail
will believe that sendmail will sell you out."
:version "24.1"
"User-supplied specification for a crude form of mailmerge capability.
When spraying is enabled, feedmail composes a list of envelope addresses.
In turn, `feedmail-spray-this-address' is temporarily set to each address
-\(stripped of any comments and angle brackets\) and a function is called which
+\(stripped of any comments and angle brackets) and a function is called which
fiddles message headers according to this variable. See the documentation for
`feedmail-fiddle-plex-blurb', for an overview of fiddle-plex data structures.
May be t, in which case a \"To:\" header is added to the message with
the stripped address as the header contents. The fiddle-plex operator
-is 'supplement.
+is `supplement'.
May be a string, in which case the string is assumed to be the name of
a message header field with the stripped address serving as the value.
-The fiddle-plex operator is 'supplement.
+The fiddle-plex operator is `supplement'.
May be a function, in which case it is called with no arguments and is
expected to return nil, t, a string, another function, or a fiddle-plex.
For example,
- (setq feedmail-spray-address-fiddle-plex-list 'feedmail-spray-via-bbdb)
+ (setq feedmail-spray-address-fiddle-plex-list \\='feedmail-spray-via-bbdb)
The idea of the example is that, during spray mode, as each message is
about to be transmitted to an individual address, the function will be
management features. Instead, arrange for this variable to be set to
the value of `buffer-file-name' before setting that to nil. An easy way
to do that would be with defadvice on `mail-send' \(undoing the
-assignments in a later advice\).
+assignments in a later advice).
feedmail will pretend that `buffer-file-name', if nil, has the value
assigned of `feedmail-queue-buffer-file-name' and carry out its normal
queueing messages or only be called for the sending of queued messages, this is
for you. Add this function to `mail-send-hook' with something like this:
- (add-hook 'mail-send-hook 'feedmail-mail-send-hook-splitter)
+ (add-hook \\='mail-send-hook \\='feedmail-mail-send-hook-splitter)
Then add the functions you want called to either `feedmail-mail-send-hook-queued'
or `feedmail-mail-send-hook', as appropriate. The distinction is that
(defun feedmail-confirm-addresses-hook-example ()
"An example of a `feedmail-last-chance-hook'.
It shows the simple addresses and gets a confirmation. Use as:
- (setq feedmail-last-chance-hook 'feedmail-confirm-addresses-hook-example)."
+ (setq feedmail-last-chance-hook \\='feedmail-confirm-addresses-hook-example)."
(save-window-excursion
(display-buffer (set-buffer (get-buffer-create " F-C-A-H-E")))
(erase-buffer)
from the queue directory. With a non-nil second argument, a brief
message is give for each file deleted. You could replace this
function, for example, to archive all of your sent messages someplace
-\(though there are better ways to get that particular result\)."
+\(though there are better ways to get that particular result)."
:group 'feedmail-queue
:type 'function
)
"/bin/rmail %s" "/bin/mail %s"))
"Command template for the subprocess which will get rid of the mail.
It can result in any command understandable by /bin/sh. Might not
-work at all in non-UNIX environments. The single '%s', if present,
+work at all in non-UNIX environments. The single `%s', if present,
gets replaced by the space-separated, simplified list of addressees.
Used in `feedmail-buffer-to-binmail' to form the shell command which
will receive the contents of the prepped buffer as stdin. The default
VAL-LIKE is not used. Else, if VAL-LIKE is a function,
it is called with two arguments: NAME and the
aggregate like values. Else, if VAL-LIKE is a string, it is
- used as a format string where a single \%s will be
+ used as a format string where a single %s will be
replaced by the aggregate values of like fields.
VAL-PRE, the results of using VAL-LIKE, and VAL-POST
feedmail FQM message file from a queue. You could use something like
this:
-\(setq auto-mode-alist \(cons \'\(\"\\\\.fqm$\" . feedmail-vm-mail-mode\) auto-mode-alist\)\)
+\(setq auto-mode-alist
+ (cons \\='(\"\\\\.fqm$\" . feedmail-vm-mail-mode) auto-mode-alist))
"
(feedmail-say-debug ">in-> feedmail-vm-mail-mode")
(let ((the-buf (current-buffer)))
(defun feedmail-message-action-help-blat (d-string)
(feedmail-say-debug ">in-> feedmail-message-action-help-blat")
(with-output-to-temp-buffer feedmail-p-h-b-n
- (princ "You're dispatching a message and feedmail queuing is enabled.
+ (princ (substitute-command-keys "\
+You're dispatching a message and feedmail queuing is enabled.
Typing ? again will normally scroll this help buffer.
Choices:
- q QUEUE for later sending \(via feedmail-run-the-queue\)
+ q QUEUE for later sending (via feedmail-run-the-queue)
Q QUEUE! like \"q\", but always make a new file
- i IMMEDIATELY send this \(but not the other queued messages\)
+ i IMMEDIATELY send this (but not the other queued messages)
I IMMEDIATELY! like \"i\", but skip following confirmation prompt
d DRAFT queue in the draft directory
D DRAFT! like \"d\", but always make a new file
- e EDIT return to the message edit buffer \(don't send or queue\)
- * SPRAY toggle spray mode \(individual message transmissions\)
- > SCROLL UP scroll message up \(toward end of message\)
- < SCROLL DOWN scroll message down \(toward beginning of message\)
+ e EDIT return to the message edit buffer (don't send or queue)
+ * SPRAY toggle spray mode (individual message transmissions)
+ > SCROLL UP scroll message up (toward end of message)
+ < SCROLL DOWN scroll message down (toward beginning of message)
? HELP show or scroll this help buffer
Synonyms:
- s SEND immediately \(same as \"i\"\)
- S SEND! immediately \(same as \"I\"\)
- r ROUGH draft \(same as \"d\"\)
- R ROUGH! draft \(same as \"D\"\)
- n NOPE didn't mean it \(same as \"e\"\)
- y YUP do the default behavior \(same as \"C-m\"\)
- SPC SCROLL UP \(same as \">\"\)
-
-The user-configurable default is currently \"")
+ s SEND immediately (same as \"i\")
+ S SEND! immediately (same as \"I\")
+ r ROUGH draft (same as \"d\")
+ R ROUGH! draft (same as \"D\")
+ n NOPE didn't mean it (same as \"e\")
+ y YUP do the default behavior (same as \"C-m\")
+ SPC SCROLL UP (same as \">\")
+
+The user-configurable default is currently \""))
(princ d-string)
(princ "\". For other possibilities,
see the variable feedmail-prompt-before-queue-user-alist.
;; the handler for the condition-case
(error (setq messages-skipped (1+ messages-skipped))
(ding t)
- (message "FQM: Trapped '%s', message left in queue." (car signal-stuff))
+ (message "FQM: Trapped `%s', message left in queue." (car signal-stuff))
(sit-for 3)
(message "FQM: Trap details: \"%s\""
(mapconcat 'identity (cdr signal-stuff) "\" \""))
(defun feedmail-queue-reminder (&optional what-event)
"Perform some kind of reminder activity about queued and draft messages.
Called with an optional symbol argument which says what kind of event
-is triggering the reminder activity. The default is 'on-demand, which
+is triggering the reminder activity. The default is `on-demand', which
is what you typically would use if you were putting this in your Emacs start-up
or mail hook code. Other recognized values for WHAT-EVENT (these are passed
internally by feedmail):