diff options
Diffstat (limited to 'lisp/mail')
| -rw-r--r-- | lisp/mail/feedmail.el | 12 | ||||
| -rw-r--r-- | lisp/mail/rfc2368.el | 8 |
2 files changed, 10 insertions, 10 deletions
diff --git a/lisp/mail/feedmail.el b/lisp/mail/feedmail.el index 14c45d1ec0b..368e2ab8982 100644 --- a/lisp/mail/feedmail.el +++ b/lisp/mail/feedmail.el @@ -418,9 +418,9 @@ cases. You can give a timeout for the prompt; see variable 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 @@ -471,9 +471,9 @@ Addresses for the message envelope are deduced by examining 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 @@ -484,7 +484,7 @@ addresses are not handled first, there can be substantial delays in 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) @@ -2054,7 +2054,7 @@ backup file names and the like)." ;; 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) "\" \"")) diff --git a/lisp/mail/rfc2368.el b/lisp/mail/rfc2368.el index 3c4e9b212b3..50ff2cfb8ea 100644 --- a/lisp/mail/rfc2368.el +++ b/lisp/mail/rfc2368.el @@ -66,16 +66,16 @@ ;; describes 'mailto:' (defconst rfc2368-mailto-scheme-index 1 - "Describes the ‘mailto:’ portion of the url.") + "Describes the `mailto:' portion of the url.") ;; i'm going to call this part the 'prequery' (defconst rfc2368-mailto-prequery-index 2 - "Describes the portion of the url between ‘mailto:’ and ‘?’.") + "Describes the portion of the url between `mailto:' and `?'.") ;; i'm going to call this part the 'query' (defconst rfc2368-mailto-query-index 4 - "Describes the portion of the url after ‘?’.") + "Describes the portion of the url after `?'.") (defun rfc2368-unhexify-string (string) - "Unhexify STRING -- e.g. ‘hello%20there’ -> ‘hello there’." + "Unhexify STRING -- e.g. `hello%20there' -> `hello there'." (replace-regexp-in-string "%[[:xdigit:]]\\{2\\}" (lambda (match) (string (string-to-number (substring match 1) |