Lines Matching +defs:sit +defs:for
13 ;; A replacement for parts of Emacs' sendmail.el (specifically,
15 ;; mode). See below for a list of additional features, including the
16 ;; ability to queue messages for later sending. If you are using
23 ;; in this release. Look for one with the next release.
36 ;; I appreciate feedback about problems you find or suggestions for
83 ;; by the separate program "fakemail" for processing outbound email.
87 ;; locally). See the variables at the top of the elisp for how to
93 ;; stimulate sending them all later (handy for laptop users);
94 ;; there is also a queue for draft messages
97 ;; be prompted for confirmation
123 ;; --- just before the optional prompt for confirmation, lets you
127 ;; --- you can specify something other than /bin/mail for the
200 ;; provide a default for generating Message-Id: header contents
204 ;; user-mail-address as default for From:
207 ;; limited support for a "drafts" directory
209 ;; allow timeout for confirmation prompt (where available)
224 ;; pause a bit for errors while running queue
237 ;; fixes to the argument conventions for the
248 ;; feedmail-deduce-bcc-where for envelope (API change for
254 ;; user can supply stuff for message action prompt
256 ;; bugfix: absolute argument to directory-files (tracked down for me
267 ;; feedmail-queue-chatty-sit-for since info is more complex sometimes
273 ;; honor mail-from-style in constructing default for feedmail-from-line
275 ;; fiddle-plexes; slightly modified semantics for feedmail-sender-line
323 "Options related to queuing messages for later sending."
336 cases. You can give a timeout for the prompt; see variable
376 Addresses for the message envelope are deduced by examining
390 seeing the message again. Some configurations of sendmail, for example,
393 is an option for either 'first or 'last because you might have a
467 ;; wait for feedmail to do it for you. (Yes, I know all about
476 default for Sender:.
484 documentation for the variable `feedmail-fiddle-plex-blurb'. In all
524 documentation for the variable `feedmail-fiddle-plex-blurb'. In all
534 to arrange for the message to get a From: line."
549 There are many and good reasons for having the message header
551 information. However, for most people and for most circumstances, it
552 is usual for them to be the same (this is probably especially true for
557 some normal way for yourself. If for some reason you want to send a
560 \"from\". This only works for mail senders which make use of
578 Moderately useful for debugging, keeping track of your correspondents'
598 documentation for the variable `feedmail-fiddle-plex-blurb'. In all
622 documentation for the variable `feedmail-fiddle-plex-blurb'. In all
626 You should let feedmail generate a Message-Id: for you unless you are sure
627 that whatever you give your messages to will do it for you (e.g., most
637 "*If non-nil, used as a suffix for generating unique Message-Id: headers.
667 documentation for the variable `feedmail-fiddle-plex-blurb'. In all
675 You should let feedmail generate a Date: for you unless you are sure
676 that whatever you give your messages to will do it for you (e.g., most
705 For an explanation of fiddle-plexes, see the documentation for the
725 Spray mode is usually pointless, and if you can't think of a good reason for
729 headers of a message. Another use is to do a crude form of mailmerge, for
742 "User-supplied specification for a crude form of mailmerge capability.
746 fiddles message headers according to this variable. See the documentation for
747 `feedmail-fiddle-plex-blurb', for an overview of fiddle-plex data structures.
750 headers for specific addresses.
765 value for this variable which consists of a single fiddle-plex must be
779 The recipe for sending form letters is: (1) create a message with all
792 "*If non-nil, provide for stashing outgoing messages in a queue.
793 This is the master on/off switch for feedmail message queuing.
794 Queuing is quite handy for laptop-based users. It's also handy if you
799 There is a separate queue for draft messages, intended to prevent
801 disk-based and intended for later transmission. The messages are
827 ;; I provided a default for VMS because someone asked for it (the
858 Default choices for the message action prompt will include sending it
869 "*A string which will be used for the message action prompt.
877 (defcustom feedmail-ask-before-queue-reprompt "FQM: Please type q, i, d, or e; or ? for help [%s]: "
878 "*A string which will be used for repompting after invalid input.
890 the help for the message action prompt."
920 "An alist of choices for the message action prompt.
922 symbol that calls up help for the prompt (the help describes the
925 The actual alist used for message action will be the standard alist
939 "User-provided supplementary help string for the message action prompt.
940 When the message action prompt is shown, the user can as for verbose help,
942 responses to the prompt. Through various customizations (see, for
981 (defcustom feedmail-queue-chatty-sit-for 2
993 The function is called during a running of the queue for sending, and
1005 (defcustom feedmail-queue-use-send-time-for-date nil
1006 "*If non-nil, use send time for the Date: header value.
1017 (defcustom feedmail-queue-use-send-time-for-message-id nil
1018 "*If non-nil, use send time for the Message-Id: header value.
1029 (defcustom feedmail-ask-for-queue-slug nil
1030 "*If non-nil, prompt user for part of the queue file name.
1032 sequence number for uniqueness, so don't specify that. feedmail will
1060 "*Indicates what to use for subject-less messages when forming a file name.
1063 If there is no subject, consult this variable. See documentation for the
1073 If the symbol 'ask, you will be prompted for a string in the mini-buffer.
1087 `feedmail-queue-draft-directory'. By the way, FQM stands for feedmail
1098 the buffer won't be reused for the next message you compose. If you
1099 are using VM for creating messages, you probably want to leave this
1100 nil, since VM has its own options for managing the recycling of
1130 being processed. This can be used for differentiating customized code
1131 for different scenarios. Users shouldn't set or change this
1137 If you have `mail-send-hook' functions that should only be called for sending/
1138 queueing messages or only be called for the sending of queued messages, this is
1139 for you. Add this function to `mail-send-hook' with something like this:
1157 "*See documentation for `feedmail-mail-send-hook-splitter'.")
1161 "*See documentation for `feedmail-mail-send-hook-splitter'.")
1186 is an empty buffer intended to soak up errors for display to the user.
1204 for display to the user. If the hook allows interactive activity, the
1228 "*Alternative header demarcation for queued messages.
1229 If you sometimes get alternative values for `mail-header-separator' in
1246 Called for each message read back out of the queue directory with a
1264 arguments: the name of the message queue file for the message just sent,
1272 message is give for each file deleted. You could replace this
1273 function, for example, to archive all of your sent messages someplace
1293 strings. Three popular choices for this are
1305 "*Command template for the subprocess which will get rid of the mail.
1314 also like to consult local mail experts for any other interesting
1322 ;; feedmail-buffer-to-smptmail are the only things provided for values
1323 ;; for the variable feedmail-buffer-eating-function. It's pretty easy
1338 Feeds the buffer to it. Probably has some flaws for Resent-* and other
1363 ;; modified to insert error for displaying
1374 (insert "Look for details below or in the *Messages* buffer.\n\n")
1395 doesn't matter in looking for headers, case of NAME is preserved when a header
1399 as described below for ACTION `combine', a list of up to three values.
1402 for ACTION (default is `supplement'):
1429 an empty string, is used as the new value for the
1431 complicated, the idea is to provide a mechanism for
1447 This is a suitable value for `send-mail-function'. It can be used
1475 (feedmail-queue-chatty-sit-for 0))
1521 (sit-for 3)
1664 (sit-for feedmail-queue-chatty-sit-for))))))
1670 (sit-for feedmail-queue-chatty-sit-for)
1672 (sit-for feedmail-queue-chatty-sit-for)))
1682 or mail hook code. Other recognized values for WHAT-EVENT (these are passed
1772 (sit-for 3)))
1803 q QUEUE for later sending (via feedmail-run-the-queue)
1833 mark for prefix sequence numbers. Subdirectories are not included in
1855 "Utility for mapping out suspect characters in a potential filename."
1856 ;; even programmers deserve a break sometimes, so cover nil for them
1858 ;; replace all non-alphanumerics with hyphen for safety
1862 ;; for tidyness, peel off leading hyphens
1864 ;; for tidyness, peel off trailing hyphens
1870 "Create a name for storing the message in the queue.
1875 mapped to mostly alphanumerics for safety."
1907 (feedmail-ask-for-queue-slug
1942 ;; convenient for moving from draft to q, for example
1955 (sit-for feedmail-queue-chatty-sit-for)))
1959 (sit-for feedmail-queue-chatty-sit-for)))))
2140 (progn (message "FQM: Sending...failed") (ding t) (sit-for 3)))
2147 (sit-for feedmail-queue-chatty-sit-for)))
2152 "Internal feedmail function for jamming fields into message header.
2154 fiddle-plex, as described in the documentation for the variable
2253 Else, look for Sender: or From: (or Resent-*) and
2339 "Default function for generating Date: header contents."
2341 (if (and (not feedmail-queue-use-send-time-for-date) maybe-file)
2378 "Default function for generating Message-Id: header contents.
2379 Based on a date and a sort of random number for tie breaking. Unless
2388 (if (and (not feedmail-queue-use-send-time-for-message-id) maybe-file)
2428 "Default function for generating X-Mailer: header contents."
2467 "Fiddle header for single spray address. Uses `feedmail-spray-this-address'."
2498 "Fiddling based on a list of fiddle-plexes for spraying."
2599 ;; look out for missing commas before continuation lines