diff options
| author | Bill Wohler | 2005-12-23 08:40:31 +0000 |
|---|---|---|
| committer | Bill Wohler | 2005-12-23 08:40:31 +0000 |
| commit | 5a4aad035fb7c3652913864e69fa095e6cb361ad (patch) | |
| tree | b2e867e6e619233fcfeb170c73a0d6da165c2ce4 | |
| parent | 4023e353eddb629784c34176bb6a462eef3cdecb (diff) | |
| download | emacs-5a4aad035fb7c3652913864e69fa095e6cb361ad.tar.gz emacs-5a4aad035fb7c3652913864e69fa095e6cb361ad.zip | |
Follow MH-E Developers Guide conventions. Use `' quotes for Help
hyperlinks such as symbols, Info nodes, or URLs. Use \" quotes for
everything else. Otherwise, you can accidently get links to
nonsense symbols.
| -rw-r--r-- | lisp/mh-e/ChangeLog | 7 | ||||
| -rw-r--r-- | lisp/mh-e/mh-acros.el | 16 | ||||
| -rw-r--r-- | lisp/mh-e/mh-alias.el | 10 | ||||
| -rw-r--r-- | lisp/mh-e/mh-comp.el | 4 | ||||
| -rw-r--r-- | lisp/mh-e/mh-customize.el | 164 | ||||
| -rw-r--r-- | lisp/mh-e/mh-e.el | 74 | ||||
| -rw-r--r-- | lisp/mh-e/mh-funcs.el | 4 | ||||
| -rw-r--r-- | lisp/mh-e/mh-identity.el | 2 | ||||
| -rw-r--r-- | lisp/mh-e/mh-inc.el | 4 | ||||
| -rw-r--r-- | lisp/mh-e/mh-index.el | 12 | ||||
| -rw-r--r-- | lisp/mh-e/mh-init.el | 10 | ||||
| -rw-r--r-- | lisp/mh-e/mh-junk.el | 48 | ||||
| -rw-r--r-- | lisp/mh-e/mh-mime.el | 6 | ||||
| -rw-r--r-- | lisp/mh-e/mh-pick.el | 6 | ||||
| -rw-r--r-- | lisp/mh-e/mh-seq.el | 14 | ||||
| -rw-r--r-- | lisp/mh-e/mh-utils.el | 10 |
16 files changed, 199 insertions, 192 deletions
diff --git a/lisp/mh-e/ChangeLog b/lisp/mh-e/ChangeLog index f6927979963..dc37b264871 100644 --- a/lisp/mh-e/ChangeLog +++ b/lisp/mh-e/ChangeLog | |||
| @@ -1,3 +1,10 @@ | |||
| 1 | 2005-12-23 Bill Wohler <wohler@newt.com> | ||
| 2 | |||
| 3 | Follow MH-E Developers Guide conventions. Use `' quotes for Help | ||
| 4 | hyperlinks such as symbols, Info nodes, or URLs. Use \" quotes for | ||
| 5 | everything else. Otherwise, you can accidently get links to | ||
| 6 | nonsense symbols. | ||
| 7 | |||
| 1 | 2005-12-22 Bill Wohler <wohler@newt.com> | 8 | 2005-12-22 Bill Wohler <wohler@newt.com> |
| 2 | 9 | ||
| 3 | Follow Emacs coding conventions. Use default setting of | 10 | Follow Emacs coding conventions. Use default setting of |
diff --git a/lisp/mh-e/mh-acros.el b/lisp/mh-e/mh-acros.el index 16c42d90634..fbc8c385863 100644 --- a/lisp/mh-e/mh-acros.el +++ b/lisp/mh-e/mh-acros.el | |||
| @@ -32,7 +32,7 @@ | |||
| 32 | ;; | 32 | ;; |
| 33 | ;; (eval-when-compile (require 'mh-acros)) | 33 | ;; (eval-when-compile (require 'mh-acros)) |
| 34 | ;; | 34 | ;; |
| 35 | ;; It is so named with a silent `m' so that it is compiled first. Otherwise, | 35 | ;; It is so named with a silent "m" so that it is compiled first. Otherwise, |
| 36 | ;; "make recompile" in Emacs 21.4 fails. | 36 | ;; "make recompile" in Emacs 21.4 fails. |
| 37 | 37 | ||
| 38 | ;;; Change Log: | 38 | ;;; Change Log: |
| @@ -47,10 +47,10 @@ | |||
| 47 | ;; routines in their macro expansions. Use mh-require-cl to provide the cl | 47 | ;; routines in their macro expansions. Use mh-require-cl to provide the cl |
| 48 | ;; routines in the best way possible. | 48 | ;; routines in the best way possible. |
| 49 | (defmacro mh-require-cl () | 49 | (defmacro mh-require-cl () |
| 50 | "Macro to load `cl' if needed. | 50 | "Macro to load \"cl\" if needed. |
| 51 | Some versions of `cl' produce code for the expansion of | 51 | Some versions of \"cl\" produce code for the expansion of |
| 52 | \(setf (gethash ...) ...) that uses functions in `cl' at run | 52 | \(setf (gethash ...) ...) that uses functions in \"cl\" at run |
| 53 | time. This macro recognizes that and loads `cl' where | 53 | time. This macro recognizes that and loads \"cl\" where |
| 54 | appropriate." | 54 | appropriate." |
| 55 | (if (eq (car (macroexpand '(setf (gethash foo bar) baz))) 'cl-puthash) | 55 | (if (eq (car (macroexpand '(setf (gethash foo bar) baz))) 'cl-puthash) |
| 56 | `(require 'cl) | 56 | `(require 'cl) |
| @@ -95,9 +95,9 @@ check if variable `transient-mark-mode' is active." | |||
| 95 | (boundp 'mark-active) mark-active)))) | 95 | (boundp 'mark-active) mark-active)))) |
| 96 | 96 | ||
| 97 | (defmacro mh-defstruct (name-spec &rest fields) | 97 | (defmacro mh-defstruct (name-spec &rest fields) |
| 98 | "Replacement for `defstruct' from the `cl' package. | 98 | "Replacement for `defstruct' from the \"cl\" package. |
| 99 | The `defstruct' in the `cl' library produces compiler warnings, | 99 | The `defstruct' in the \"cl\" library produces compiler warnings, |
| 100 | and generates code that uses functions present in `cl' at | 100 | and generates code that uses functions present in \"cl\" at |
| 101 | run-time. This is a partial replacement, that avoids these | 101 | run-time. This is a partial replacement, that avoids these |
| 102 | issues. | 102 | issues. |
| 103 | 103 | ||
diff --git a/lisp/mh-e/mh-alias.el b/lisp/mh-e/mh-alias.el index f0eb08939dc..397cd9ea782 100644 --- a/lisp/mh-e/mh-alias.el +++ b/lisp/mh-e/mh-alias.el | |||
| @@ -70,7 +70,7 @@ | |||
| 70 | "*A list of system files which are a source of aliases. | 70 | "*A list of system files which are a source of aliases. |
| 71 | If these files are modified, they are automatically reread. This list | 71 | If these files are modified, they are automatically reread. This list |
| 72 | need include only system aliases and the passwd file, since personal | 72 | need include only system aliases and the passwd file, since personal |
| 73 | alias files listed in your `Aliasfile:' MH profile component are | 73 | alias files listed in your \"Aliasfile:\" MH profile component are |
| 74 | automatically included. You can update the alias list manually using | 74 | automatically included. You can update the alias list manually using |
| 75 | \\[mh-alias-reload].") | 75 | \\[mh-alias-reload].") |
| 76 | 76 | ||
| @@ -146,7 +146,7 @@ COMMA-SEPARATOR is non-nil." | |||
| 146 | 146 | ||
| 147 | (defun mh-alias-local-users () | 147 | (defun mh-alias-local-users () |
| 148 | "Return an alist of local users from /etc/passwd. | 148 | "Return an alist of local users from /etc/passwd. |
| 149 | Exclude all aliases already in `mh-alias-alist' from `ali'" | 149 | Exclude all aliases already in `mh-alias-alist' from \"ali\"" |
| 150 | (let (passwd-alist) | 150 | (let (passwd-alist) |
| 151 | (save-excursion | 151 | (save-excursion |
| 152 | (set-buffer (get-buffer-create mh-temp-buffer)) | 152 | (set-buffer (get-buffer-create mh-temp-buffer)) |
| @@ -188,7 +188,7 @@ Exclude all aliases already in `mh-alias-alist' from `ali'" | |||
| 188 | 188 | ||
| 189 | Since aliases are updated frequently, MH-E reloads aliases | 189 | Since aliases are updated frequently, MH-E reloads aliases |
| 190 | automatically whenever an alias lookup occurs if an alias source has | 190 | automatically whenever an alias lookup occurs if an alias source has |
| 191 | changed. Sources include files listed in your `Aliasfile:' profile | 191 | changed. Sources include files listed in your \"Aliasfile:\" profile |
| 192 | component and your password file if option `mh-alias-local-users' is | 192 | component and your password file if option `mh-alias-local-users' is |
| 193 | turned on. However, you can reload your aliases manually by calling | 193 | turned on. However, you can reload your aliases manually by calling |
| 194 | this command directly. | 194 | this command directly. |
| @@ -422,7 +422,7 @@ string is converted to lower case." | |||
| 422 | (defun mh-alias-insert-file (&optional alias) | 422 | (defun mh-alias-insert-file (&optional alias) |
| 423 | "Return filename which should be used to add ALIAS. | 423 | "Return filename which should be used to add ALIAS. |
| 424 | The value of the option `mh-alias-insert-file' is used if non-nil\; | 424 | The value of the option `mh-alias-insert-file' is used if non-nil\; |
| 425 | otherwise the value of the `Aliasfile:' profile component is used. | 425 | otherwise the value of the \"Aliasfile:\" profile component is used. |
| 426 | If the alias already exists, try to return the name of the file that | 426 | If the alias already exists, try to return the name of the file that |
| 427 | contains it." | 427 | contains it." |
| 428 | (cond | 428 | (cond |
| @@ -449,7 +449,7 @@ contains it." | |||
| 449 | (cond | 449 | (cond |
| 450 | ((not autolist) | 450 | ((not autolist) |
| 451 | (error "No writable alias file. | 451 | (error "No writable alias file. |
| 452 | Set `mh-alias-insert-file' or the Aliasfile profile component")) | 452 | Set `mh-alias-insert-file' or the \"Aliasfile:\" profile component")) |
| 453 | ((not (elt autolist 1)) ; Only one entry, use it | 453 | ((not (elt autolist 1)) ; Only one entry, use it |
| 454 | (car autolist)) | 454 | (car autolist)) |
| 455 | ((or (not alias) | 455 | ((or (not alias) |
diff --git a/lisp/mh-e/mh-comp.el b/lisp/mh-e/mh-comp.el index 5a3807e967e..898f24dccb7 100644 --- a/lisp/mh-e/mh-comp.el +++ b/lisp/mh-e/mh-comp.el | |||
| @@ -162,8 +162,8 @@ user's MH directory, then in the system MH lib directory.") | |||
| 162 | 162 | ||
| 163 | (defvar mh-new-draft-cleaned-headers | 163 | (defvar mh-new-draft-cleaned-headers |
| 164 | "^Date:\\|^Received:\\|^Message-Id:\\|^From:\\|^Sender:\\|^Errors-To:\\|^Delivery-Date:\\|^Return-Path:" | 164 | "^Date:\\|^Received:\\|^Message-Id:\\|^From:\\|^Sender:\\|^Errors-To:\\|^Delivery-Date:\\|^Return-Path:" |
| 165 | "Regexp of header lines to remove before offering a message as a new draft. | 165 | "Regexp of header lines to remove before offering a message as a new draft\\<mh-folder-mode-map>. |
| 166 | Used by the \\<mh-folder-mode-map>`\\[mh-edit-again]' and `\\[mh-extract-rejected-mail]' commands.") | 166 | Used by the \\[mh-edit-again] and \\[mh-extract-rejected-mail] commands.") |
| 167 | 167 | ||
| 168 | (defvar mh-to-field-choices '(("t" . "To:") ("s" . "Subject:") ("c" . "Cc:") | 168 | (defvar mh-to-field-choices '(("t" . "To:") ("s" . "Subject:") ("c" . "Cc:") |
| 169 | ("b" . "Bcc:") ("f" . "Fcc:") ("r" . "From:") | 169 | ("b" . "Bcc:") ("f" . "Fcc:") ("r" . "From:") |
diff --git a/lisp/mh-e/mh-customize.el b/lisp/mh-e/mh-customize.el index 6aa28a3c960..f5556bda2ba 100644 --- a/lisp/mh-e/mh-customize.el +++ b/lisp/mh-e/mh-customize.el | |||
| @@ -271,14 +271,14 @@ See `mh-variant'." | |||
| 271 | (defcustom mh-variant 'autodetect | 271 | (defcustom mh-variant 'autodetect |
| 272 | "*Specifies the variant used by MH-E. | 272 | "*Specifies the variant used by MH-E. |
| 273 | 273 | ||
| 274 | The default setting of this option is `Auto-detect' which means | 274 | The default setting of this option is \"Auto-detect\" which means |
| 275 | that MH-E will automatically choose the first of nmh, MH, or GNU | 275 | that MH-E will automatically choose the first of nmh, MH, or GNU |
| 276 | mailutils that it finds in the directories listed in | 276 | mailutils that it finds in the directories listed in |
| 277 | `mh-path' (which you can customize), `mh-sys-path', and | 277 | `mh-path' (which you can customize), `mh-sys-path', and |
| 278 | `exec-path'. If, for example, you have both nmh and mailutils | 278 | `exec-path'. If, for example, you have both nmh and mailutils |
| 279 | installed and `mh-variant-in-use' was initialized to nmh but you | 279 | installed and `mh-variant-in-use' was initialized to nmh but you |
| 280 | want to use mailutils, then you can set this option to | 280 | want to use mailutils, then you can set this option to |
| 281 | `mailutils'. | 281 | \"mailutils\". |
| 282 | 282 | ||
| 283 | When this variable is changed, MH-E resets `mh-progs', `mh-lib', | 283 | When this variable is changed, MH-E resets `mh-progs', `mh-lib', |
| 284 | `mh-lib-progs', `mh-flists-present-flag', and `mh-variant-in-use' | 284 | `mh-lib-progs', `mh-flists-present-flag', and `mh-variant-in-use' |
| @@ -329,10 +329,10 @@ does not display a warning if the alias is not found." | |||
| 329 | (defcustom mh-alias-insert-file nil | 329 | (defcustom mh-alias-insert-file nil |
| 330 | "*Filename used to store a new MH-E alias. | 330 | "*Filename used to store a new MH-E alias. |
| 331 | 331 | ||
| 332 | The default setting of this option is `Use Aliasfile Profile | 332 | The default setting of this option is \"Use Aliasfile Profile |
| 333 | Component'. This option can also hold the name of a file or a | 333 | Component\". This option can also hold the name of a file or a |
| 334 | list a file names. If this option is set to a list of file names, | 334 | list a file names. If this option is set to a list of file names, |
| 335 | or the `Aliasfile:' profile component contains more than one file | 335 | or the \"Aliasfile:\" profile component contains more than one file |
| 336 | name, MH-E will prompt for one of them when MH-E adds an alias." | 336 | name, MH-E will prompt for one of them when MH-E adds an alias." |
| 337 | :type '(choice (const :tag "Use Aliasfile Profile Component" nil) | 337 | :type '(choice (const :tag "Use Aliasfile Profile Component" nil) |
| 338 | (file :tag "Alias File") | 338 | (file :tag "Alias File") |
| @@ -342,9 +342,9 @@ name, MH-E will prompt for one of them when MH-E adds an alias." | |||
| 342 | (defcustom mh-alias-insertion-location 'sorted | 342 | (defcustom mh-alias-insertion-location 'sorted |
| 343 | "Specifies where new aliases are entered in alias files. | 343 | "Specifies where new aliases are entered in alias files. |
| 344 | 344 | ||
| 345 | This option is set to `Alphabetical' by default. If you organize | 345 | This option is set to \"Alphabetical\" by default. If you organize |
| 346 | your alias file in other ways, then adding aliases to the `Top' | 346 | your alias file in other ways, then adding aliases to the \"Top\" |
| 347 | or `Bottom' of your alias file might be more appropriate." | 347 | or \"Bottom\" of your alias file might be more appropriate." |
| 348 | :type '(choice (const :tag "Alphabetical" sorted) | 348 | :type '(choice (const :tag "Alphabetical" sorted) |
| 349 | (const :tag "Top" top) | 349 | (const :tag "Top" top) |
| 350 | (const :tag "Bottom" bottom)) | 350 | (const :tag "Bottom" bottom)) |
| @@ -353,12 +353,12 @@ or `Bottom' of your alias file might be more appropriate." | |||
| 353 | (defcustom mh-alias-local-users t | 353 | (defcustom mh-alias-local-users t |
| 354 | "*If on, local users are added to alias completion. | 354 | "*If on, local users are added to alias completion. |
| 355 | 355 | ||
| 356 | Aliases are created from `/etc/passwd' entries with a user ID | 356 | Aliases are created from \"/etc/passwd\" entries with a user ID |
| 357 | larger than a magical number, typically 200. This can be a handy | 357 | larger than a magical number, typically 200. This can be a handy |
| 358 | tool on a machine where you and co-workers exchange messages. | 358 | tool on a machine where you and co-workers exchange messages. |
| 359 | These aliases have the form `local.first.last' if a real name is | 359 | These aliases have the form \"local.first.last\" if a real name is |
| 360 | present in the password file. Otherwise, the alias will have the | 360 | present in the password file. Otherwise, the alias will have the |
| 361 | form `local.login'. | 361 | form \"local.login\". |
| 362 | 362 | ||
| 363 | If you're on a system with thousands of users you don't know, and | 363 | If you're on a system with thousands of users you don't know, and |
| 364 | the loading of local aliases slows MH-E down noticeably, then | 364 | the loading of local aliases slows MH-E down noticeably, then |
| @@ -372,7 +372,7 @@ NIS password file." | |||
| 372 | 372 | ||
| 373 | (defcustom mh-alias-local-users-prefix "local." | 373 | (defcustom mh-alias-local-users-prefix "local." |
| 374 | "*String prefixed to the real names of users from the password file. | 374 | "*String prefixed to the real names of users from the password file. |
| 375 | This option can also be set to `Use Login'. | 375 | This option can also be set to \"Use Login\". |
| 376 | 376 | ||
| 377 | For example, consider the following password file entry: | 377 | For example, consider the following password file entry: |
| 378 | 378 | ||
| @@ -474,11 +474,11 @@ an alternate view. For example, \"'(\"-nolimit\" \"-textfield\" | |||
| 474 | ;;; Folder Selection (:group 'mh-folder-selection) | 474 | ;;; Folder Selection (:group 'mh-folder-selection) |
| 475 | 475 | ||
| 476 | (defcustom mh-default-folder-for-message-function nil | 476 | (defcustom mh-default-folder-for-message-function nil |
| 477 | "Function to select a default folder for refiling or `Fcc'. | 477 | "Function to select a default folder for refiling or \"Fcc\". |
| 478 | 478 | ||
| 479 | The current buffer is set to the message being refiled with point | 479 | The current buffer is set to the message being refiled with point |
| 480 | at the start of the message. This function should return the | 480 | at the start of the message. This function should return the |
| 481 | default folder as a string with a leading `+' sign. It can also | 481 | default folder as a string with a leading \"+\" sign. It can also |
| 482 | return nil so that the last folder name is used as the default, | 482 | return nil so that the last folder name is used as the default, |
| 483 | or an empty string to suppress the default entirely." | 483 | or an empty string to suppress the default entirely." |
| 484 | :type 'function | 484 | :type 'function |
| @@ -489,7 +489,7 @@ or an empty string to suppress the default entirely." | |||
| 489 | 489 | ||
| 490 | The folder name associated with the first address found in this | 490 | The folder name associated with the first address found in this |
| 491 | list is used as the default for `mh-refile-msg' and similar | 491 | list is used as the default for `mh-refile-msg' and similar |
| 492 | functions. Each element in this list contains a `Check Recipient' | 492 | functions. Each element in this list contains a \"Check Recipient\" |
| 493 | item. If this item is turned on, then the address is checked | 493 | item. If this item is turned on, then the address is checked |
| 494 | against the recipient instead of the sender. This is useful for | 494 | against the recipient instead of the sender. This is useful for |
| 495 | mailing lists. | 495 | mailing lists. |
| @@ -530,35 +530,35 @@ for more information." | |||
| 530 | (defcustom mh-identity-list nil | 530 | (defcustom mh-identity-list nil |
| 531 | "*List of identities. | 531 | "*List of identities. |
| 532 | 532 | ||
| 533 | To customize this option, click on the `INS' button and enter a label | 533 | To customize this option, click on the \"INS\" button and enter a label |
| 534 | such as `Home' or `Work'. Then click on the `INS' button with the | 534 | such as \"Home\" or \"Work\". Then click on the \"INS\" button with the |
| 535 | label `Add at least one item below'. Then choose one of the items in | 535 | label \"Add at least one item below\". Then choose one of the items in |
| 536 | the `Value Menu'. | 536 | the \"Value Menu\". |
| 537 | 537 | ||
| 538 | You can specify an alternate `From:' header field using the `From | 538 | You can specify an alternate \"From:\" header field using the \"From |
| 539 | Field' menu item. You must include a valid email address. A standard | 539 | Field\" menu item. You must include a valid email address. A standard |
| 540 | format is `First Last <login@@host.domain>'. If you use an initial | 540 | format is \"First Last <login@@host.domain>\". If you use an initial |
| 541 | with a period, then you must quote your name as in `\"First I. Last\" | 541 | with a period, then you must quote your name as in '\"First I. Last\" |
| 542 | <login@@host.domain>'. People usually list the name of the company | 542 | <login@@host.domain>'. People usually list the name of the company |
| 543 | where they work using the `Organization Field' menu item. Set any | 543 | where they work using the \"Organization Field\" menu item. Set any |
| 544 | arbitrary header field and value in the `Other Field' menu item. | 544 | arbitrary header field and value in the \"Other Field\" menu item. |
| 545 | Unless the header field is a standard one, precede the name of your | 545 | Unless the header field is a standard one, precede the name of your |
| 546 | field's label with `X-', as in `X-Fruit-of-the-Day:'. The value of | 546 | field's label with \"X-\", as in \"X-Fruit-of-the-Day:\". The value of |
| 547 | `Attribution Verb' overrides the setting of | 547 | \"Attribution Verb\" overrides the setting of |
| 548 | `mh-extract-from-attribution-verb'. Set your signature with the | 548 | `mh-extract-from-attribution-verb'. Set your signature with the |
| 549 | `Signature' menu item. You can specify the contents of | 549 | \"Signature\" menu item. You can specify the contents of |
| 550 | `mh-signature-file-name', a file, or a function. Specify a different | 550 | `mh-signature-file-name', a file, or a function. Specify a different |
| 551 | key to sign or encrypt messages with the `GPG Key ID' menu item. | 551 | key to sign or encrypt messages with the \"GPG Key ID\" menu item. |
| 552 | 552 | ||
| 553 | You can select the identities you have added via the menu called | 553 | You can select the identities you have added via the menu called |
| 554 | `Identity' in the MH-Letter buffer. You can also use | 554 | \"Identity\" in the MH-Letter buffer. You can also use |
| 555 | \\[mh-insert-identity]. To clear the fields and signature added by the | 555 | \\[mh-insert-identity]. To clear the fields and signature added by the |
| 556 | identity, select the `None' identity. | 556 | identity, select the \"None\" identity. |
| 557 | 557 | ||
| 558 | The `Identity' menu contains two other items to save you from having | 558 | The \"Identity\" menu contains two other items to save you from having |
| 559 | to set the identity on every message. The menu item `Set Default for | 559 | to set the identity on every message. The menu item \"Set Default for |
| 560 | Session' can be used to set the default identity to the current | 560 | Session\" can be used to set the default identity to the current |
| 561 | identity until you exit Emacs. The menu item `Save as Default' sets | 561 | identity until you exit Emacs. The menu item \"Save as Default\" sets |
| 562 | the option `mh-identity-default' to the current identity setting. You | 562 | the option `mh-identity-default' to the current identity setting. You |
| 563 | can also customize the `mh-identity-default' option in the usual | 563 | can also customize the `mh-identity-default' option in the usual |
| 564 | fashion." | 564 | fashion." |
| @@ -597,31 +597,31 @@ fashion." | |||
| 597 | "List of recipients for which header lines are automatically inserted. | 597 | "List of recipients for which header lines are automatically inserted. |
| 598 | 598 | ||
| 599 | This option can be used to set the identity depending on the | 599 | This option can be used to set the identity depending on the |
| 600 | recipient. To customize this option, click on the `INS' button and | 600 | recipient. To customize this option, click on the \"INS\" button and |
| 601 | enter a regular expression for the recipient's address. Click on the | 601 | enter a regular expression for the recipient's address. Click on the |
| 602 | `INS' button with the `Add at least one item below' label. Then choose | 602 | \"INS\" button with the \"Add at least one item below\" label. Then choose |
| 603 | one of the items in the `Value Menu'. | 603 | one of the items in the \"Value Menu\". |
| 604 | 604 | ||
| 605 | The `Identity' menu item is used to select an identity from those | 605 | The \"Identity\" menu item is used to select an identity from those |
| 606 | configured in `mh-identity-list'. All of the information for that | 606 | configured in `mh-identity-list'. All of the information for that |
| 607 | identity will be added if the recipient matches. The `Fcc Field' menu | 607 | identity will be added if the recipient matches. The \"Fcc Field\" menu |
| 608 | item is used to select a folder that is used in the `Fcc:' header. | 608 | item is used to select a folder that is used in the \"Fcc:\" header. |
| 609 | When you send the message, MH will put a copy of your message in this | 609 | When you send the message, MH will put a copy of your message in this |
| 610 | folder. The `Mail-Followup-To Field' menu item is used to insert an | 610 | folder. The \"Mail-Followup-To Field\" menu item is used to insert an |
| 611 | `Mail-Followup-To:' header field with the recipients you provide. If | 611 | \"Mail-Followup-To:\" header field with the recipients you provide. If |
| 612 | the recipient's mail user agent supports this header field (as nmh | 612 | the recipient's mail user agent supports this header field (as nmh |
| 613 | does), then their replies will go to the addresses listed. This is | 613 | does), then their replies will go to the addresses listed. This is |
| 614 | useful if their replies go both to the list and to you and you don't | 614 | useful if their replies go both to the list and to you and you don't |
| 615 | have a mechanism to suppress duplicates. If you reply to someone not | 615 | have a mechanism to suppress duplicates. If you reply to someone not |
| 616 | on the list, you must either remove the `Mail-Followup-To:' field, or | 616 | on the list, you must either remove the \"Mail-Followup-To:\" field, or |
| 617 | ensure the recipient is also listed there so that he receives replies | 617 | ensure the recipient is also listed there so that he receives replies |
| 618 | to your reply. Other header fields may be added using the `Other | 618 | to your reply. Other header fields may be added using the \"Other |
| 619 | Field' menu item. | 619 | Field\" menu item. |
| 620 | 620 | ||
| 621 | These fields can only be added after the recipient is known. Once the | 621 | These fields can only be added after the recipient is known. Once the |
| 622 | header contains one or more recipients, run the | 622 | header contains one or more recipients, run the |
| 623 | \\[mh-insert-auto-fields] command or choose the `Identity -> Insert | 623 | \\[mh-insert-auto-fields] command or choose the \"Identity -> Insert |
| 624 | Auto Fields' menu item to insert these fields manually. However, you | 624 | Auto Fields\" menu item to insert these fields manually. However, you |
| 625 | can just send the message and the fields will be added automatically. | 625 | can just send the message and the fields will be added automatically. |
| 626 | You are given a chance to see these fields and to confirm them before | 626 | You are given a chance to see these fields and to confirm them before |
| 627 | the message is actually sent. You can do away with this confirmation | 627 | the message is actually sent. You can do away with this confirmation |
| @@ -682,22 +682,22 @@ and attributions in `mh-identity-list' are added. To customize | |||
| 682 | `mh-identity-handlers', replace the name of an existing handler | 682 | `mh-identity-handlers', replace the name of an existing handler |
| 683 | function associated with the field you want to change with the | 683 | function associated with the field you want to change with the |
| 684 | name of a function you have written. You can also click on an | 684 | name of a function you have written. You can also click on an |
| 685 | `INS' button and insert a field of your choice and the name of | 685 | \"INS\" button and insert a field of your choice and the name of |
| 686 | the function you have written to handle it. | 686 | the function you have written to handle it. |
| 687 | 687 | ||
| 688 | The `Field' field can be any field that you've used in your | 688 | The \"Field\" field can be any field that you've used in your |
| 689 | `mh-identity-list'. The special fields `:attribution-verb', | 689 | `mh-identity-list'. The special fields \":attribution-verb\", |
| 690 | `:signature', or `:pgg-default-user-id' are used for the | 690 | \":signature\", or \":pgg-default-user-id\" are used for the |
| 691 | `mh-identity-list' choices `Attribution Verb', `Signature', and | 691 | `mh-identity-list' choices \"Attribution Verb\", \"Signature\", and |
| 692 | `GPG Key ID' respectively. | 692 | \"GPG Key ID\" respectively. |
| 693 | 693 | ||
| 694 | The handler associated with the `:default' field is used when no | 694 | The handler associated with the \":default\" field is used when no |
| 695 | other field matches. | 695 | other field matches. |
| 696 | 696 | ||
| 697 | The handler functions are passed two or three arguments: the | 697 | The handler functions are passed two or three arguments: the |
| 698 | FIELD itself (for example, `From'), or one of the special | 698 | FIELD itself (for example, \"From\"), or one of the special |
| 699 | fields (for example, `:signature'), and the ACTION `'remove' or | 699 | fields (for example, \":signature\"), and the ACTION 'remove or |
| 700 | `'add'. If the action is `'add', an additional argument | 700 | 'add. If the action is 'add, an additional argument |
| 701 | containing the VALUE for the field is given." | 701 | containing the VALUE for the field is given." |
| 702 | :type '(repeat (cons (string :tag "Field") function)) | 702 | :type '(repeat (cons (string :tag "Field") function)) |
| 703 | :group 'mh-identity) | 703 | :group 'mh-identity) |
| @@ -712,7 +712,7 @@ containing the VALUE for the field is given." | |||
| 712 | This program generates a one-line summary for each of the new | 712 | This program generates a one-line summary for each of the new |
| 713 | messages. Unless it is an absolute pathname, the file is assumed | 713 | messages. Unless it is an absolute pathname, the file is assumed |
| 714 | to be in the `mh-progs' directory. You may also link a file to | 714 | to be in the `mh-progs' directory. You may also link a file to |
| 715 | `inc' that uses a different format. You'll then need to modify | 715 | \"inc\" that uses a different format. You'll then need to modify |
| 716 | several scan line format variables appropriately." | 716 | several scan line format variables appropriately." |
| 717 | :type 'string | 717 | :type 'string |
| 718 | :group 'mh-inc) | 718 | :group 'mh-inc) |
| @@ -722,25 +722,25 @@ several scan line format variables appropriately." | |||
| 722 | 722 | ||
| 723 | You can use the `mh-inc-spool-list' variable to direct MH-E to | 723 | You can use the `mh-inc-spool-list' variable to direct MH-E to |
| 724 | retrieve mail from arbitrary spool files other than your system | 724 | retrieve mail from arbitrary spool files other than your system |
| 725 | mailbox, file it in folders other than your `+inbox', and assign | 725 | mailbox, file it in folders other than your \"+inbox\", and assign |
| 726 | key bindings to incorporate this mail. | 726 | key bindings to incorporate this mail. |
| 727 | 727 | ||
| 728 | Suppose you are subscribed to the `mh-e-devel' mailing list and | 728 | Suppose you are subscribed to the \"mh-e-devel\" mailing list and |
| 729 | you use `procmail' to filter this mail into `~/mail/mh-e' with | 729 | you use \"procmail\" to filter this mail into \"~/mail/mh-e\" with |
| 730 | the following recipe in `.procmailrc': | 730 | the following recipe in \".procmailrc\": |
| 731 | 731 | ||
| 732 | MAILDIR=$HOME/mail | 732 | MAILDIR=$HOME/mail |
| 733 | :0: | 733 | :0: |
| 734 | * ^From mh-e-devel-admin@stop.mail-abuse.org | 734 | * ^From mh-e-devel-admin@stop.mail-abuse.org |
| 735 | mh-e | 735 | mh-e |
| 736 | 736 | ||
| 737 | In order to incorporate `~/mail/mh-e' into `+mh-e' with an `I m' | 737 | In order to incorporate \"~/mail/mh-e\" into \"+mh-e\" with an |
| 738 | \(`mh-inc-spool-mh-e'\) command, customize this option, and click | 738 | \"I m\" (mh-inc-spool-mh-e) command, customize this option, and click |
| 739 | on the `INS' button. Enter a `Spool File' of `~/mail/mh-e', a | 739 | on the \"INS\" button. Enter a \"Spool File\" of \"~/mail/mh-e\", a |
| 740 | `Folder' of `mh-e', and a `Key Binding' of `m'. | 740 | \"Folder\" of \"mh-e\", and a \"Key Binding\" of \"m\". |
| 741 | 741 | ||
| 742 | You can use `xbuffy' to automate the incorporation of this mail | 742 | You can use \"xbuffy\" to automate the incorporation of this mail |
| 743 | using the `gnudoit' command in the `gnuserv' package as follows: | 743 | using the \"gnudoit\" command in the \"gnuserv\" package as follows: |
| 744 | 744 | ||
| 745 | box ~/mail/mh-e | 745 | box ~/mail/mh-e |
| 746 | title mh-e | 746 | title mh-e |
| @@ -761,11 +761,11 @@ using the `gnudoit' command in the `gnuserv' package as follows: | |||
| 761 | (defcustom mh-index-program nil | 761 | (defcustom mh-index-program nil |
| 762 | "Indexing program that MH-E shall use. | 762 | "Indexing program that MH-E shall use. |
| 763 | 763 | ||
| 764 | The default setting of this option is `Auto-detect' which means | 764 | The default setting of this option is \"Auto-detect\" which means |
| 765 | that MH-E will automatically choose one of swish++, swish-e, | 765 | that MH-E will automatically choose one of swish++, swish-e, |
| 766 | mairix, namazu, pick and grep in that order. If, for example, you | 766 | mairix, namazu, pick and grep in that order. If, for example, you |
| 767 | have both swish++ and mairix installed and you want to use | 767 | have both swish++ and mairix installed and you want to use |
| 768 | mairix, then you can set this option to `mairix'. | 768 | mairix, then you can set this option to \"mairix\". |
| 769 | 769 | ||
| 770 | More information about setting up an indexing program to use with | 770 | More information about setting up an indexing program to use with |
| 771 | MH-E can be found in the documentation of `mh-index-search'." | 771 | MH-E can be found in the documentation of `mh-index-search'." |
| @@ -1269,7 +1269,7 @@ there isn't much advantage to that." | |||
| 1269 | :group 'mh-sequences) | 1269 | :group 'mh-sequences) |
| 1270 | 1270 | ||
| 1271 | (defcustom mh-update-sequences-after-mh-show-flag t | 1271 | (defcustom mh-update-sequences-after-mh-show-flag t |
| 1272 | "*Non-nil means flush MH sequences to disk after message is shown. | 1272 | "*Non-nil means flush MH sequences to disk after message is shown\\<mh-folder-mode-map>. |
| 1273 | 1273 | ||
| 1274 | Three sequences are maintained internally by MH-E and pushed out | 1274 | Three sequences are maintained internally by MH-E and pushed out |
| 1275 | to MH when a message is shown. They include the sequence | 1275 | to MH when a message is shown. They include the sequence |
| @@ -1277,8 +1277,8 @@ specified by your \"Unseen-Sequence:\" profile entry, \"cur\", | |||
| 1277 | and the sequence listed by the option `mh-tick-seq' which is | 1277 | and the sequence listed by the option `mh-tick-seq' which is |
| 1278 | \"tick\" by default. If you do not like this behavior, turn off | 1278 | \"tick\" by default. If you do not like this behavior, turn off |
| 1279 | this option. You can then update the state manually with the | 1279 | this option. You can then update the state manually with the |
| 1280 | `\\[mh-execute-commands]', `\\[mh-quit]', or | 1280 | \\[mh-execute-commands], \\[mh-quit], or \\[mh-update-sequences] |
| 1281 | `\\[mh-update-sequences]' commands." | 1281 | commands." |
| 1282 | :type 'boolean | 1282 | :type 'boolean |
| 1283 | :group 'mh-sequences) | 1283 | :group 'mh-sequences) |
| 1284 | 1284 | ||
| @@ -1681,7 +1681,7 @@ See also `mh-clean-message-header-flag'." | |||
| 1681 | Header fields that you would like to hide that aren't listed in | 1681 | Header fields that you would like to hide that aren't listed in |
| 1682 | `mh-invisible-header-fields-default' can be added to this option | 1682 | `mh-invisible-header-fields-default' can be added to this option |
| 1683 | with a couple of caveats. Regular expressions are not allowed. | 1683 | with a couple of caveats. Regular expressions are not allowed. |
| 1684 | Unique fields should have a `:' suffix; otherwise, the element | 1684 | Unique fields should have a \":\" suffix; otherwise, the element |
| 1685 | can be used to render invisible an entire class of fields that | 1685 | can be used to render invisible an entire class of fields that |
| 1686 | start with the same prefix. If you think a header field should be | 1686 | start with the same prefix. If you think a header field should be |
| 1687 | generally ignored, report a bug (see URL | 1687 | generally ignored, report a bug (see URL |
| @@ -1862,8 +1862,8 @@ The option `mh-fetch-x-image-url' controls the fetching of the | |||
| 1862 | "*Default directory for \\<mh-folder-mode-map>\\[mh-store-msg]. | 1862 | "*Default directory for \\<mh-folder-mode-map>\\[mh-store-msg]. |
| 1863 | 1863 | ||
| 1864 | If you would like to change the initial default directory, | 1864 | If you would like to change the initial default directory, |
| 1865 | customize this option, change the value from `Current' to | 1865 | customize this option, change the value from \"Current\" to |
| 1866 | `Directory', and then enter the name of the directory for storing | 1866 | \"Directory\", and then enter the name of the directory for storing |
| 1867 | the content of these messages." | 1867 | the content of these messages." |
| 1868 | :type '(choice (const :tag "Current" nil) | 1868 | :type '(choice (const :tag "Current" nil) |
| 1869 | directory) | 1869 | directory) |
| @@ -2027,16 +2027,16 @@ where, | |||
| 2027 | FUNCTION is the name of the function that will be executed when | 2027 | FUNCTION is the name of the function that will be executed when |
| 2028 | the button is clicked. | 2028 | the button is clicked. |
| 2029 | 2029 | ||
| 2030 | MODES is a list of symbols. List elements must be from `folder', | 2030 | MODES is a list of symbols. List elements must be from \"folder\", |
| 2031 | `letter' and `sequence'. If `folder' is present then the button is | 2031 | \"letter\" and \"sequence\". If \"folder\" is present then the button is |
| 2032 | available in the folder and show buffer. If the name of FUNCTION is | 2032 | available in the folder and show buffer. If the name of FUNCTION is |
| 2033 | of the form \"mh-foo\", where foo is some arbitrary string, then we | 2033 | of the form \"mh-foo\", where foo is some arbitrary string, then we |
| 2034 | check if the function `mh-show-foo' exists. If it exists then that | 2034 | check if the function `mh-show-foo' exists. If it exists then that |
| 2035 | function is used in the show buffer. Otherwise the original function | 2035 | function is used in the show buffer. Otherwise the original function |
| 2036 | `mh-foo' is used in the show buffer as well. Presence of `sequence' | 2036 | `mh-foo' is used in the show buffer as well. Presence of \"sequence\" |
| 2037 | is handled similar to the above. The only difference is that the | 2037 | is handled similar to the above. The only difference is that the |
| 2038 | button is shown only when the folder is narrowed to a sequence. If | 2038 | button is shown only when the folder is narrowed to a sequence. If |
| 2039 | `letter' is present in MODES, then the button is available during | 2039 | \"letter\" is present in MODES, then the button is available during |
| 2040 | draft editing and runs FUNCTION when clicked. | 2040 | draft editing and runs FUNCTION when clicked. |
| 2041 | 2041 | ||
| 2042 | ICON is the icon that is drawn in the button. | 2042 | ICON is the icon that is drawn in the button. |
| @@ -2048,7 +2048,7 @@ where, | |||
| 2048 | 2048 | ||
| 2049 | Optional item ENABLE-EXPR is an arbitrary lisp expression. If it | 2049 | Optional item ENABLE-EXPR is an arbitrary lisp expression. If it |
| 2050 | evaluates to nil, then the button is deactivated, otherwise it is | 2050 | evaluates to nil, then the button is deactivated, otherwise it is |
| 2051 | active. If is in't present then the button is always active." | 2051 | active. If it isn't present then the button is always active." |
| 2052 | ;; The following variable names have been carefully chosen to make code | 2052 | ;; The following variable names have been carefully chosen to make code |
| 2053 | ;; generation easier. Modifying the names should be done carefully. | 2053 | ;; generation easier. Modifying the names should be done carefully. |
| 2054 | (let (folder-buttons folder-docs folder-button-setter sequence-button-setter | 2054 | (let (folder-buttons folder-docs folder-button-setter sequence-button-setter |
diff --git a/lisp/mh-e/mh-e.el b/lisp/mh-e/mh-e.el index 6160b8874dc..d75457bd203 100644 --- a/lisp/mh-e/mh-e.el +++ b/lisp/mh-e/mh-e.el | |||
| @@ -139,10 +139,10 @@ argument. This format is identical to the default except that | |||
| 139 | additional hints for fontification have been added to the fifth | 139 | additional hints for fontification have been added to the fifth |
| 140 | column (remember that in Emacs, the first column is 0). | 140 | column (remember that in Emacs, the first column is 0). |
| 141 | 141 | ||
| 142 | The values of the fifth column, in priority order, are: `-' if | 142 | The values of the fifth column, in priority order, are: \"-\" if |
| 143 | the message has been replied to, t if an address on the To: line | 143 | the message has been replied to, t if an address on the To: line |
| 144 | matches one of the mailboxes of the current user, `c' if the Cc: | 144 | matches one of the mailboxes of the current user, \"c\" if the Cc: |
| 145 | line matches, `b' if the Bcc: line matches, and `n' if a | 145 | line matches, \"b\" if the Bcc: line matches, and \"n\" if a |
| 146 | non-empty Newsgroups: header is present.") | 146 | non-empty Newsgroups: header is present.") |
| 147 | 147 | ||
| 148 | (defvar mh-scan-format-nmh | 148 | (defvar mh-scan-format-nmh |
| @@ -165,10 +165,10 @@ This format is identical to the default except that additional | |||
| 165 | hints for fontification have been added to the fifth | 165 | hints for fontification have been added to the fifth |
| 166 | column (remember that in Emacs, the first column is 0). | 166 | column (remember that in Emacs, the first column is 0). |
| 167 | 167 | ||
| 168 | The values of the fifth column, in priority order, are: `-' if | 168 | The values of the fifth column, in priority order, are: \"-\" if |
| 169 | the message has been replied to, t if an address on the To: field | 169 | the message has been replied to, t if an address on the To: field |
| 170 | matches one of the mailboxes of the current user, `c' if the Cc: | 170 | matches one of the mailboxes of the current user, \"c\" if the Cc: |
| 171 | field matches, `b' if the Bcc: field matches, and `n' if a | 171 | field matches, \"b\" if the Bcc: field matches, and \"n\" if a |
| 172 | non-empty Newsgroups: field is present.") | 172 | non-empty Newsgroups: field is present.") |
| 173 | 173 | ||
| 174 | (defvar mh-note-deleted ?D | 174 | (defvar mh-note-deleted ?D |
| @@ -266,7 +266,7 @@ is not correct, the date will not be highlighted. See also | |||
| 266 | 266 | ||
| 267 | Note that the default setting of `mh-folder-font-lock-keywords' | 267 | Note that the default setting of `mh-folder-font-lock-keywords' |
| 268 | expects this expression to contain two parenthesized expressions. | 268 | expects this expression to contain two parenthesized expressions. |
| 269 | The first is expected to match the `To:' that the default scan | 269 | The first is expected to match the \"To:\" that the default scan |
| 270 | format file generates. The second is expected to match the | 270 | format file generates. The second is expected to match the |
| 271 | recipient's name as in the default of | 271 | recipient's name as in the default of |
| 272 | \"\\\\(To:\\\\)\\\\(..............\\\\)\". If this regular | 272 | \"\\\\(To:\\\\)\\\\(..............\\\\)\". If this regular |
| @@ -289,9 +289,9 @@ not correct, the body fragment will not be highlighted.") | |||
| 289 | It must match from the beginning of the line. Note that the | 289 | It must match from the beginning of the line. Note that the |
| 290 | default setting of `mh-folder-font-lock-keywords' expects this | 290 | default setting of `mh-folder-font-lock-keywords' expects this |
| 291 | expression to contain at least three parenthesized expressions. | 291 | expression to contain at least three parenthesized expressions. |
| 292 | The first is expected to match the `Re:' string, if any. The | 292 | The first is expected to match the \"Re:\" string, if any. The |
| 293 | second matches an optional bracketed number after `Re:', such as | 293 | second matches an optional bracketed number after \"Re:\", such as |
| 294 | in `Re[2]:' (and is thus a sub-expression of the first | 294 | in \"Re[2]:\" (and is thus a sub-expression of the first |
| 295 | expression) and the third is expected to match the subject line | 295 | expression) and the third is expected to match the subject line |
| 296 | itself as in the default of (broken on multiple lines for | 296 | itself as in the default of (broken on multiple lines for |
| 297 | readability): | 297 | readability): |
| @@ -356,26 +356,26 @@ the sender will not be highlighted.") | |||
| 356 | (defvar mh-scan-cmd-note-width 1 | 356 | (defvar mh-scan-cmd-note-width 1 |
| 357 | "Number of columns consumed by the cmd-note field in `mh-scan-format'. | 357 | "Number of columns consumed by the cmd-note field in `mh-scan-format'. |
| 358 | 358 | ||
| 359 | This column will have one of the values: ` ', `D', `^', `+' and | 359 | This column will have one of the values: \" \", \"D\", \"^\", \"+\" and |
| 360 | where ` ' is the default value, | 360 | where \" \" is the default value, |
| 361 | 361 | ||
| 362 | `D' is the `mh-note-deleted' character, | 362 | \"D\" is the `mh-note-deleted' character, |
| 363 | `^' is the `mh-note-refiled' character, and | 363 | \"^\" is the `mh-note-refiled' character, and |
| 364 | `+' is the `mh-note-cur' character.") | 364 | \"+\" is the `mh-note-cur' character.") |
| 365 | 365 | ||
| 366 | (defvar mh-scan-destination-width 1 | 366 | (defvar mh-scan-destination-width 1 |
| 367 | "Number of columns consumed by the destination field in `mh-scan-format'. | 367 | "Number of columns consumed by the destination field in `mh-scan-format'. |
| 368 | 368 | ||
| 369 | This column will have one of ' ', '%', '-', 't', 'c', 'b', or `n' | 369 | This column will have one of \" \", \"%\", \"-\", \"t\", \"c\", \"b\", or \"n\" |
| 370 | in it. | 370 | in it. |
| 371 | 371 | ||
| 372 | ' ' blank space is the default character. | 372 | \" \" blank space is the default character. |
| 373 | '%' indicates that the message in in a named MH sequence. | 373 | \"%\" indicates that the message in in a named MH sequence. |
| 374 | '-' indicates that the message has been annotated with a replied field. | 374 | \"-\" indicates that the message has been annotated with a replied field. |
| 375 | 't' indicates that the message contains mymbox in the To: field. | 375 | \"t\" indicates that the message contains mymbox in the To: field. |
| 376 | 'c' indicates that the message contains mymbox in the Cc: field. | 376 | \"c\" indicates that the message contains mymbox in the Cc: field. |
| 377 | 'b' indicates that the message contains mymbox in the Bcc: field. | 377 | \"b\" indicates that the message contains mymbox in the Bcc: field. |
| 378 | 'n' indicates that the message contains a Newsgroups: field.") | 378 | \"n\" indicates that the message contains a Newsgroups: field.") |
| 379 | 379 | ||
| 380 | (defvar mh-scan-date-width 5 | 380 | (defvar mh-scan-date-width 5 |
| 381 | "Number of columns consumed by the date field in `mh-scan-format'. | 381 | "Number of columns consumed by the date field in `mh-scan-format'. |
| @@ -383,7 +383,7 @@ This column will typically be of the form mm/dd.") | |||
| 383 | 383 | ||
| 384 | (defvar mh-scan-date-flag-width 1 | 384 | (defvar mh-scan-date-flag-width 1 |
| 385 | "Number of columns consumed to flag (in)valid dates in `mh-scan-format'. | 385 | "Number of columns consumed to flag (in)valid dates in `mh-scan-format'. |
| 386 | This column will have ` ' for valid and `*' for invalid or | 386 | This column will have \" \" for valid and \"*\" for invalid or |
| 387 | missing dates.") | 387 | missing dates.") |
| 388 | 388 | ||
| 389 | (defvar mh-scan-from-mbox-width 17 | 389 | (defvar mh-scan-from-mbox-width 17 |
| @@ -778,7 +778,7 @@ The name of the folder is derived as follows: | |||
| 778 | 778 | ||
| 779 | a) The folder name associated with the first address found in | 779 | a) The folder name associated with the first address found in |
| 780 | the list `mh-default-folder-list' is used. Each element in | 780 | the list `mh-default-folder-list' is used. Each element in |
| 781 | this list contains a `Check Recipient' item. If this item is | 781 | this list contains a \"Check Recipient\" item. If this item is |
| 782 | turned on, then the address is checked against the recipient | 782 | turned on, then the address is checked against the recipient |
| 783 | instead of the sender. This is useful for mailing lists. | 783 | instead of the sender. This is useful for mailing lists. |
| 784 | 784 | ||
| @@ -1370,7 +1370,7 @@ folders whose names end with a '+' character." | |||
| 1370 | (values (format "+%s" folder) (car unseen) (car total)))))))) | 1370 | (values (format "+%s" folder) (car unseen) (car total)))))))) |
| 1371 | 1371 | ||
| 1372 | (defun mh-folder-size-folder (folder) | 1372 | (defun mh-folder-size-folder (folder) |
| 1373 | "Find size of FOLDER using `folder'." | 1373 | "Find size of FOLDER using \"folder\"." |
| 1374 | (with-temp-buffer | 1374 | (with-temp-buffer |
| 1375 | (let ((u (length (cdr (assoc mh-unseen-seq | 1375 | (let ((u (length (cdr (assoc mh-unseen-seq |
| 1376 | (mh-read-folder-sequences folder nil)))))) | 1376 | (mh-read-folder-sequences folder nil)))))) |
| @@ -1382,7 +1382,7 @@ folders whose names end with a '+' character." | |||
| 1382 | (values 0 u folder))))) | 1382 | (values 0 u folder))))) |
| 1383 | 1383 | ||
| 1384 | (defun mh-folder-size-flist (folder) | 1384 | (defun mh-folder-size-flist (folder) |
| 1385 | "Find size of FOLDER using `flist'." | 1385 | "Find size of FOLDER using \"flist\"." |
| 1386 | (with-temp-buffer | 1386 | (with-temp-buffer |
| 1387 | (call-process (expand-file-name "flist" mh-progs) nil t nil "-showzero" | 1387 | (call-process (expand-file-name "flist" mh-progs) nil t nil "-showzero" |
| 1388 | "-norecurse" folder "-sequence" (symbol-name mh-unseen-seq)) | 1388 | "-norecurse" folder "-sequence" (symbol-name mh-unseen-seq)) |
| @@ -1789,20 +1789,20 @@ page): | |||
| 1789 | Indicates all messages in the range <num1> to <num2>, inclusive. | 1789 | Indicates all messages in the range <num1> to <num2>, inclusive. |
| 1790 | The range must be nonempty. | 1790 | The range must be nonempty. |
| 1791 | 1791 | ||
| 1792 | `<num>:N' | 1792 | <num>:N |
| 1793 | `<num>:+N' | 1793 | <num>:+N |
| 1794 | `<num>:-N' | 1794 | <num>:-N |
| 1795 | Up to N messages beginning with (or ending with) message num. Num | 1795 | Up to N messages beginning with (or ending with) message num. Num |
| 1796 | may be any of the predefined symbols: first, prev, cur, next or | 1796 | may be any of the predefined symbols: first, prev, cur, next or |
| 1797 | last. | 1797 | last. |
| 1798 | 1798 | ||
| 1799 | `first:N' | 1799 | first:N |
| 1800 | `prev:N' | 1800 | prev:N |
| 1801 | `next:N' | 1801 | next:N |
| 1802 | `last:N' | 1802 | last:N |
| 1803 | The first, previous, next or last messages, if they exist. | 1803 | The first, previous, next or last messages, if they exist. |
| 1804 | 1804 | ||
| 1805 | `all' | 1805 | all |
| 1806 | All of the messages. | 1806 | All of the messages. |
| 1807 | 1807 | ||
| 1808 | For example, a range that shows all of these things is `1 2 3 | 1808 | For example, a range that shows all of these things is `1 2 3 |
| @@ -2643,7 +2643,7 @@ in list." | |||
| 2643 | (defalias 'mh-alt-send 'mh-send) | 2643 | (defalias 'mh-alt-send 'mh-send) |
| 2644 | (defalias 'mh-alt-visit-folder 'mh-visit-folder) | 2644 | (defalias 'mh-alt-visit-folder 'mh-visit-folder) |
| 2645 | 2645 | ||
| 2646 | ;; Save the `b' binding for a future `back'. Maybe? | 2646 | ;; Save the "b" binding for a future `back'. Maybe? |
| 2647 | (gnus-define-keys mh-folder-mode-map | 2647 | (gnus-define-keys mh-folder-mode-map |
| 2648 | " " mh-page-msg | 2648 | " " mh-page-msg |
| 2649 | "!" mh-refile-or-write-again | 2649 | "!" mh-refile-or-write-again |
| @@ -2793,7 +2793,7 @@ in list." | |||
| 2793 | ;; | 2793 | ;; |
| 2794 | ;; When adding a new prefix, ensure that the help message contains "what" the | 2794 | ;; When adding a new prefix, ensure that the help message contains "what" the |
| 2795 | ;; prefix is for. For example, if the word "folder" were not present in the | 2795 | ;; prefix is for. For example, if the word "folder" were not present in the |
| 2796 | ;; `F' entry, it would not be clear what these commands operated upon. | 2796 | ;; "F" entry, it would not be clear what these commands operated upon. |
| 2797 | (defvar mh-help-messages | 2797 | (defvar mh-help-messages |
| 2798 | '((nil "[i]nc, [.]show, [,]show all, [n]ext, [p]revious,\n" | 2798 | '((nil "[i]nc, [.]show, [,]show all, [n]ext, [p]revious,\n" |
| 2799 | "[d]elete, [o]refile, e[x]ecute,\n" | 2799 | "[d]elete, [o]refile, e[x]ecute,\n" |
diff --git a/lisp/mh-e/mh-funcs.el b/lisp/mh-e/mh-funcs.el index df39ca72cf0..800ff96b510 100644 --- a/lisp/mh-e/mh-funcs.el +++ b/lisp/mh-e/mh-funcs.el | |||
| @@ -303,7 +303,7 @@ the optional argument EXTRA-ARGS is given." | |||
| 303 | 303 | ||
| 304 | ;;;###mh-autoload | 304 | ;;;###mh-autoload |
| 305 | (defun mh-store-msg (directory) | 305 | (defun mh-store-msg (directory) |
| 306 | "Unpack message created with `uudecode' or `shar'. | 306 | "Unpack message created with \"uudecode\" or \"shar\". |
| 307 | 307 | ||
| 308 | The default DIRECTORY for extraction is the current directory; | 308 | The default DIRECTORY for extraction is the current directory; |
| 309 | however, you have a chance to specify a different extraction | 309 | however, you have a chance to specify a different extraction |
| @@ -409,7 +409,7 @@ value of `mh-store-default-directory' or the current directory." | |||
| 409 | (defun mh-prefix-help () | 409 | (defun mh-prefix-help () |
| 410 | "Display cheat sheet for the commands of the current prefix in minibuffer." | 410 | "Display cheat sheet for the commands of the current prefix in minibuffer." |
| 411 | (interactive) | 411 | (interactive) |
| 412 | ;; We got here because the user pressed a `?', but he pressed a prefix key | 412 | ;; We got here because the user pressed a "?", but he pressed a prefix key |
| 413 | ;; before that. Since the the key vector starts at index 0, the index of the | 413 | ;; before that. Since the the key vector starts at index 0, the index of the |
| 414 | ;; last keystroke is length-1 and thus the second to last keystroke is at | 414 | ;; last keystroke is length-1 and thus the second to last keystroke is at |
| 415 | ;; length-2. We use that information to obtain a suitable prefix character | 415 | ;; length-2. We use that information to obtain a suitable prefix character |
diff --git a/lisp/mh-e/mh-identity.el b/lisp/mh-e/mh-identity.el index 508b747718c..52bb8f903fe 100644 --- a/lisp/mh-e/mh-identity.el +++ b/lisp/mh-e/mh-identity.el | |||
| @@ -122,7 +122,7 @@ Return t if anything is deleted." | |||
| 122 | (defun mh-identity-field-handler (field) | 122 | (defun mh-identity-field-handler (field) |
| 123 | "Return the handler for header FIELD or nil if none set. | 123 | "Return the handler for header FIELD or nil if none set. |
| 124 | The field name is downcased. If the FIELD begins with the | 124 | The field name is downcased. If the FIELD begins with the |
| 125 | character `:', then it must have a special handler defined in | 125 | character \":\", then it must have a special handler defined in |
| 126 | `mh-identity-handlers', else return an error since it is not a | 126 | `mh-identity-handlers', else return an error since it is not a |
| 127 | valid header field." | 127 | valid header field." |
| 128 | (or (cdr (mh-assoc-ignore-case field mh-identity-handlers)) | 128 | (or (cdr (mh-assoc-ignore-case field mh-identity-handlers)) |
diff --git a/lisp/mh-e/mh-inc.el b/lisp/mh-e/mh-inc.el index d5becd26ce4..51f84f7fb38 100644 --- a/lisp/mh-e/mh-inc.el +++ b/lisp/mh-e/mh-inc.el | |||
| @@ -1,4 +1,4 @@ | |||
| 1 | ;;; mh-inc.el --- MH-E `inc' and separate mail spool handling | 1 | ;;; mh-inc.el --- MH-E "inc" and separate mail spool handling |
| 2 | ;; | 2 | ;; |
| 3 | ;; Copyright (C) 2003, 2004 Free Software Foundation, Inc. | 3 | ;; Copyright (C) 2003, 2004 Free Software Foundation, Inc. |
| 4 | 4 | ||
| @@ -28,7 +28,7 @@ | |||
| 28 | 28 | ||
| 29 | ;; Support for inc. In addition to reading from the system mailbox, inc can | 29 | ;; Support for inc. In addition to reading from the system mailbox, inc can |
| 30 | ;; also be used to incorporate mail from multiple spool files into separate | 30 | ;; also be used to incorporate mail from multiple spool files into separate |
| 31 | ;; folders. See `C-h v mh-inc-spool-list'. | 31 | ;; folders. See "C-h v mh-inc-spool-list". |
| 32 | 32 | ||
| 33 | ;;; Change Log: | 33 | ;;; Change Log: |
| 34 | 34 | ||
diff --git a/lisp/mh-e/mh-index.el b/lisp/mh-e/mh-index.el index d0bab9d120f..c8ec7fb399b 100644 --- a/lisp/mh-e/mh-index.el +++ b/lisp/mh-e/mh-index.el | |||
| @@ -362,14 +362,14 @@ construct the base name." | |||
| 362 | Use a prefix argument to repeat the search. | 362 | Use a prefix argument to repeat the search. |
| 363 | 363 | ||
| 364 | Unlike regular searches, the prompt for the folder to search can be | 364 | Unlike regular searches, the prompt for the folder to search can be |
| 365 | `all' to search all folders; in addition, the search works recursively | 365 | \"all\" to search all folders; in addition, the search works recursively |
| 366 | on the listed folder. The search criteria are entered in an MH-Pick | 366 | on the listed folder. The search criteria are entered in an MH-Pick |
| 367 | buffer as described in `mh-search-folder'. | 367 | buffer as described in `mh-search-folder'. |
| 368 | 368 | ||
| 369 | To perform the search, type \\<mh-pick-mode-map>\\[mh-do-search]. | 369 | To perform the search, type \\<mh-pick-mode-map>\\[mh-do-search]. |
| 370 | Another difference from the regular searches is that because the | 370 | Another difference from the regular searches is that because the |
| 371 | search operates on more than one folder, the messages that are found | 371 | search operates on more than one folder, the messages that are found |
| 372 | are put in a temporary sub-folder of `+mhe-index' and are displayed in | 372 | are put in a temporary sub-folder of \"+mhe-index\" and are displayed in |
| 373 | an MH-Folder buffer. This buffer is special because it displays | 373 | an MH-Folder buffer. This buffer is special because it displays |
| 374 | messages from multiple folders; each set of messages from a given | 374 | messages from multiple folders; each set of messages from a given |
| 375 | folder has a heading with the folder name. | 375 | folder has a heading with the folder name. |
| @@ -554,7 +554,7 @@ search results." | |||
| 554 | "Write index data to file." | 554 | "Write index data to file." |
| 555 | (ignore-errors | 555 | (ignore-errors |
| 556 | (unless (eq major-mode 'mh-folder-mode) | 556 | (unless (eq major-mode 'mh-folder-mode) |
| 557 | (error "Can't be called from folder in `%s'" major-mode)) | 557 | (error "Can't be called from folder in \"%s\"" major-mode)) |
| 558 | (let ((data mh-index-data) | 558 | (let ((data mh-index-data) |
| 559 | (msg-checksum-map mh-index-msg-checksum-map) | 559 | (msg-checksum-map mh-index-msg-checksum-map) |
| 560 | (checksum-origin-map mh-index-checksum-origin-map) | 560 | (checksum-origin-map mh-index-checksum-origin-map) |
| @@ -576,7 +576,7 @@ search results." | |||
| 576 | "Read index data from file." | 576 | "Read index data from file." |
| 577 | (ignore-errors | 577 | (ignore-errors |
| 578 | (unless (eq major-mode 'mh-folder-mode) | 578 | (unless (eq major-mode 'mh-folder-mode) |
| 579 | (error "Can't be called from folder in `%s'" major-mode)) | 579 | (error "Can't be called from folder in \"%s\"" major-mode)) |
| 580 | (let ((infile (concat buffer-file-name mh-index-data-file)) | 580 | (let ((infile (concat buffer-file-name mh-index-data-file)) |
| 581 | t1 t2 t3 t4 t5) | 581 | t1 t2 t3 t4 t5) |
| 582 | (with-temp-buffer | 582 | (with-temp-buffer |
| @@ -1352,9 +1352,9 @@ folders." | |||
| 1352 | (defun mh-index-new-messages (folders) | 1352 | (defun mh-index-new-messages (folders) |
| 1353 | "Display unseen messages. | 1353 | "Display unseen messages. |
| 1354 | 1354 | ||
| 1355 | If you use a program such as `procmail' to use `rcvstore' to file | 1355 | If you use a program such as \"procmail\" to use \"rcvstore\" to file |
| 1356 | your incoming mail automatically, you can display new, unseen, | 1356 | your incoming mail automatically, you can display new, unseen, |
| 1357 | messages using this command. All messages in the `unseen' | 1357 | messages using this command. All messages in the \"unseen\" |
| 1358 | sequence from the folders in `mh-new-messages-folders' are | 1358 | sequence from the folders in `mh-new-messages-folders' are |
| 1359 | listed. | 1359 | listed. |
| 1360 | 1360 | ||
diff --git a/lisp/mh-e/mh-init.el b/lisp/mh-e/mh-init.el index 7b8477a4a94..6b8feda8ccc 100644 --- a/lisp/mh-e/mh-init.el +++ b/lisp/mh-e/mh-init.el | |||
| @@ -64,7 +64,7 @@ This directory contains, among other things, the components file.") | |||
| 64 | This directory contains, among other things, the mhl program.") | 64 | This directory contains, among other things, the mhl program.") |
| 65 | 65 | ||
| 66 | (defvar mh-flists-present-flag nil | 66 | (defvar mh-flists-present-flag nil |
| 67 | "Non-nil means that we have `flists'.") | 67 | "Non-nil means that we have \"flists\".") |
| 68 | 68 | ||
| 69 | ;;;###autoload | 69 | ;;;###autoload |
| 70 | (put 'mh-progs 'risky-local-variable t) | 70 | (put 'mh-progs 'risky-local-variable t) |
| @@ -101,14 +101,14 @@ is described by the variable `mh-variants'." | |||
| 101 | (defvar mh-variant-in-use nil | 101 | (defvar mh-variant-in-use nil |
| 102 | "The MH variant currently in use; a string with variant and version number. | 102 | "The MH variant currently in use; a string with variant and version number. |
| 103 | This differs from `mh-variant' when the latter is set to | 103 | This differs from `mh-variant' when the latter is set to |
| 104 | `autodetect'.") | 104 | \"autodetect\".") |
| 105 | 105 | ||
| 106 | ;;;###mh-autoload | 106 | ;;;###mh-autoload |
| 107 | (defun mh-variant-set (variant) | 107 | (defun mh-variant-set (variant) |
| 108 | "Set the MH variant to VARIANT. | 108 | "Set the MH variant to VARIANT. |
| 109 | Sets `mh-progs', `mh-lib', `mh-lib-progs' and | 109 | Sets `mh-progs', `mh-lib', `mh-lib-progs' and |
| 110 | `mh-flists-present-flag'. | 110 | `mh-flists-present-flag'. |
| 111 | If the VARIANT is `autodetect', then first try nmh, then MH and | 111 | If the VARIANT is \"autodetect\", then first try nmh, then MH and |
| 112 | finally GNU mailutils." | 112 | finally GNU mailutils." |
| 113 | (interactive | 113 | (interactive |
| 114 | (list (completing-read | 114 | (list (completing-read |
| @@ -202,7 +202,7 @@ directories to the customizable variable `mh-path'.") | |||
| 202 | (defun mh-variant-mh-info (dir) | 202 | (defun mh-variant-mh-info (dir) |
| 203 | "Return info for MH variant in DIR assuming a temporary buffer is setup." | 203 | "Return info for MH variant in DIR assuming a temporary buffer is setup." |
| 204 | ;; MH does not have the -version option. | 204 | ;; MH does not have the -version option. |
| 205 | ;; Its version number is included in the output of `-help' as: | 205 | ;; Its version number is included in the output of "-help" as: |
| 206 | ;; | 206 | ;; |
| 207 | ;; version: MH 6.8.4 #2[UCI] (burrito) of Fri Jan 15 20:01:39 EST 1999 | 207 | ;; version: MH 6.8.4 #2[UCI] (burrito) of Fri Jan 15 20:01:39 EST 1999 |
| 208 | ;; options: [ATHENA] [BIND] [DUMB] [LIBLOCKFILE] [LOCALE] [MAILGROUP] [MHE] | 208 | ;; options: [ATHENA] [BIND] [DUMB] [LIBLOCKFILE] [LOCALE] [MAILGROUP] [MHE] |
| @@ -306,7 +306,7 @@ This assumes that a temporary buffer is setup." | |||
| 306 | (defun mh-image-load-path () | 306 | (defun mh-image-load-path () |
| 307 | "Ensure that the MH-E images are accessible by `find-image'. | 307 | "Ensure that the MH-E images are accessible by `find-image'. |
| 308 | Images for MH-E are found in ../../etc/images relative to the | 308 | Images for MH-E are found in ../../etc/images relative to the |
| 309 | files in `lisp/mh-e'. If `image-load-path' exists (since Emacs | 309 | files in \"lisp/mh-e\". If `image-load-path' exists (since Emacs |
| 310 | 22), then the images directory is added to it if isn't already | 310 | 22), then the images directory is added to it if isn't already |
| 311 | there. Otherwise, the images directory is added to the | 311 | there. Otherwise, the images directory is added to the |
| 312 | `load-path' if it isn't already there." | 312 | `load-path' if it isn't already there." |
diff --git a/lisp/mh-e/mh-junk.el b/lisp/mh-e/mh-junk.el index 70012163698..5d2bf87581e 100644 --- a/lisp/mh-e/mh-junk.el +++ b/lisp/mh-e/mh-junk.el | |||
| @@ -111,7 +111,7 @@ RANGE is read in interactive use." | |||
| 111 | SpamAssassin is one of the more popular spam filtering programs. Get | 111 | SpamAssassin is one of the more popular spam filtering programs. Get |
| 112 | it from your local distribution or from http://spamassassin.org/. | 112 | it from your local distribution or from http://spamassassin.org/. |
| 113 | 113 | ||
| 114 | To use SpamAssassin, add the following recipes to `.procmailrc': | 114 | To use SpamAssassin, add the following recipes to \".procmailrc\": |
| 115 | 115 | ||
| 116 | MAILDIR=$HOME/`mhparam Path` | 116 | MAILDIR=$HOME/`mhparam Path` |
| 117 | 117 | ||
| @@ -128,57 +128,57 @@ To use SpamAssassin, add the following recipes to `.procmailrc': | |||
| 128 | * ^X-Spam-Status: Yes | 128 | * ^X-Spam-Status: Yes |
| 129 | spam/. | 129 | spam/. |
| 130 | 130 | ||
| 131 | If you don't use `spamc', use `spamassassin -P -a'. | 131 | If you don't use \"spamc\", use \"spamassassin -P -a\". |
| 132 | 132 | ||
| 133 | Note that one of the recipes above throws away messages with a score | 133 | Note that one of the recipes above throws away messages with a score |
| 134 | greater than or equal to 10. Here's how you can determine a value that | 134 | greater than or equal to 10. Here's how you can determine a value that |
| 135 | works best for you. | 135 | works best for you. |
| 136 | 136 | ||
| 137 | First, run `spamassassin -t' on every mail message in your archive and | 137 | First, run \"spamassassin -t\" on every mail message in your archive and |
| 138 | use Gnumeric to verify that the average plus the standard deviation of | 138 | use Gnumeric to verify that the average plus the standard deviation of |
| 139 | good mail is under 5, the SpamAssassin default for \"spam\". | 139 | good mail is under 5, the SpamAssassin default for \"spam\". |
| 140 | 140 | ||
| 141 | Using Gnumeric, sort the messages by score and view the messages with | 141 | Using Gnumeric, sort the messages by score and view the messages with |
| 142 | the highest score. Determine the score which encompasses all of your | 142 | the highest score. Determine the score which encompasses all of your |
| 143 | interesting messages and add a couple of points to be conservative. | 143 | interesting messages and add a couple of points to be conservative. |
| 144 | Add that many dots to the `X-Spam-Level:' header field above to send | 144 | Add that many dots to the \"X-Spam-Level:\" header field above to send |
| 145 | messages with that score down the drain. | 145 | messages with that score down the drain. |
| 146 | 146 | ||
| 147 | In the example above, messages with a score of 5-9 are set aside in | 147 | In the example above, messages with a score of 5-9 are set aside in |
| 148 | the `+spam' folder for later review. The major weakness of rules-based | 148 | the \"+spam\" folder for later review. The major weakness of rules-based |
| 149 | filters is a plethora of false positives so it is worthwhile to check. | 149 | filters is a plethora of false positives so it is worthwhile to check. |
| 150 | 150 | ||
| 151 | If SpamAssassin classifies a message incorrectly, or is unsure, you | 151 | If SpamAssassin classifies a message incorrectly, or is unsure, you |
| 152 | can use the MH-E commands \\[mh-junk-blacklist] and | 152 | can use the MH-E commands \\[mh-junk-blacklist] and |
| 153 | \\[mh-junk-whitelist]. | 153 | \\[mh-junk-whitelist]. |
| 154 | 154 | ||
| 155 | The \\[mh-junk-blacklist] command adds a `blacklist_from' entry to | 155 | The \\[mh-junk-blacklist] command adds a \"blacklist_from\" entry to |
| 156 | `~/spamassassin/user_prefs', deletes the message, and sends the | 156 | \"~/spamassassin/user_prefs\", deletes the message, and sends the |
| 157 | message to the Razor, so that others might not see this spam. If the | 157 | message to the Razor, so that others might not see this spam. If the |
| 158 | `sa-learn' command is available, the message is also recategorized as | 158 | \"sa-learn\" command is available, the message is also recategorized as |
| 159 | spam. | 159 | spam. |
| 160 | 160 | ||
| 161 | The \\[mh-junk-whitelist] command adds a `whitelist_from' rule to the | 161 | The \\[mh-junk-whitelist] command adds a \"whitelist_from\" rule to the |
| 162 | `~/.spamassassin/user_prefs' file. If the `sa-learn' command is | 162 | \"~/.spamassassin/user_prefs\" file. If the \"sa-learn\" command is |
| 163 | available, the message is also recategorized as ham. | 163 | available, the message is also recategorized as ham. |
| 164 | 164 | ||
| 165 | Over time, you'll observe that the same host or domain occurs | 165 | Over time, you'll observe that the same host or domain occurs |
| 166 | repeatedly in the `blacklist_from' entries, so you might think that | 166 | repeatedly in the \"blacklist_from\" entries, so you might think that |
| 167 | you could avoid future spam by blacklisting all mail from a particular | 167 | you could avoid future spam by blacklisting all mail from a particular |
| 168 | domain. The utility function `mh-spamassassin-identify-spammers' helps | 168 | domain. The utility function `mh-spamassassin-identify-spammers' helps |
| 169 | you do precisely that. This function displays a frequency count of the | 169 | you do precisely that. This function displays a frequency count of the |
| 170 | hosts and domains in the `blacklist_from' entries from the last blank | 170 | hosts and domains in the \"blacklist_from\" entries from the last blank |
| 171 | line in `~/.spamassassin/user_prefs' to the end of the file. This | 171 | line in \"~/.spamassassin/user_prefs\" to the end of the file. This |
| 172 | information can be used so that you can replace multiple | 172 | information can be used so that you can replace multiple |
| 173 | `blacklist_from' entries with a single wildcard entry such as: | 173 | \"blacklist_from\" entries with a single wildcard entry such as: |
| 174 | 174 | ||
| 175 | blacklist_from *@*amazingoffersdirect2u.com | 175 | blacklist_from *@*amazingoffersdirect2u.com |
| 176 | 176 | ||
| 177 | In versions of SpamAssassin (2.50 and on) that support a Bayesian | 177 | In versions of SpamAssassin (2.50 and on) that support a Bayesian |
| 178 | classifier, \\[mh-junk-blacklist] uses the `sa-learn' program to | 178 | classifier, \\[mh-junk-blacklist] uses the \"sa-learn\" program to |
| 179 | recategorize the message as spam. Neither MH-E, nor SpamAssassin, | 179 | recategorize the message as spam. Neither MH-E, nor SpamAssassin, |
| 180 | rebuilds the database after adding words, so you will need to run | 180 | rebuilds the database after adding words, so you will need to run |
| 181 | `sa-learn --rebuild' periodically. This can be done by adding the | 181 | \"sa-learn --rebuild\" periodically. This can be done by adding the |
| 182 | following to your crontab: | 182 | following to your crontab: |
| 183 | 183 | ||
| 184 | 0 * * * * sa-learn --rebuild > /dev/null 2>&1" | 184 | 0 * * * * sa-learn --rebuild > /dev/null 2>&1" |
| @@ -215,8 +215,8 @@ following to your crontab: | |||
| 215 | (defun mh-spamassassin-whitelist (msg) | 215 | (defun mh-spamassassin-whitelist (msg) |
| 216 | "Whitelist MSG with SpamAssassin. | 216 | "Whitelist MSG with SpamAssassin. |
| 217 | 217 | ||
| 218 | The \\[mh-junk-whitelist] command adds a `whitelist_from' rule to | 218 | The \\[mh-junk-whitelist] command adds a \"whitelist_from\" rule to |
| 219 | the `~/.spamassassin/user_prefs' file. If the `sa-learn' command | 219 | the \"~/.spamassassin/user_prefs\" file. If the \"sa-learn\" command |
| 220 | is available, the message is also recategorized as ham. | 220 | is available, the message is also recategorized as ham. |
| 221 | 221 | ||
| 222 | See `mh-spamassassin-blacklist' for more information." | 222 | See `mh-spamassassin-blacklist' for more information." |
| @@ -249,7 +249,7 @@ See `mh-spamassassin-blacklist' for more information." | |||
| 249 | (message "Whitelisting message %d...done" msg)))) | 249 | (message "Whitelisting message %d...done" msg)))) |
| 250 | 250 | ||
| 251 | (defun mh-spamassassin-add-rule (rule body) | 251 | (defun mh-spamassassin-add-rule (rule body) |
| 252 | "Add a new rule to `~/.spamassassin/user_prefs'. | 252 | "Add a new rule to \"~/.spamassassin/user_prefs\". |
| 253 | The name of the rule is RULE and its body is BODY." | 253 | The name of the rule is RULE and its body is BODY." |
| 254 | (save-window-excursion | 254 | (save-window-excursion |
| 255 | (let* ((line (format "%s\t%s\n" rule body)) | 255 | (let* ((line (format "%s\t%s\n" rule body)) |
| @@ -269,10 +269,10 @@ The name of the rule is RULE and its body is BODY." | |||
| 269 | "Identify spammers who are repeat offenders. | 269 | "Identify spammers who are repeat offenders. |
| 270 | 270 | ||
| 271 | This function displays a frequency count of the hosts and domains | 271 | This function displays a frequency count of the hosts and domains |
| 272 | in the `blacklist_from' entries from the last blank line in | 272 | in the \"blacklist_from\" entries from the last blank line in |
| 273 | `~/.spamassassin/user_prefs' to the end of the file. This | 273 | \"~/.spamassassin/user_prefs\" to the end of the file. This |
| 274 | information can be used so that you can replace multiple | 274 | information can be used so that you can replace multiple |
| 275 | `blacklist_from' entries with a single wildcard entry such as: | 275 | \"blacklist_from\" entries with a single wildcard entry such as: |
| 276 | 276 | ||
| 277 | blacklist_from *@*amazingoffersdirect2u.com" | 277 | blacklist_from *@*amazingoffersdirect2u.com" |
| 278 | (interactive) | 278 | (interactive) |
| @@ -333,7 +333,7 @@ training methods are described in the FAQ that is distributed with | |||
| 333 | bogofilter. Note that most Bayesian filters need 1000 to 5000 of each | 333 | bogofilter. Note that most Bayesian filters need 1000 to 5000 of each |
| 334 | type of message to start doing a good job. | 334 | type of message to start doing a good job. |
| 335 | 335 | ||
| 336 | To use bogofilter, add the following recipes to `.procmailrc': | 336 | To use bogofilter, add the following recipes to \".procmailrc\": |
| 337 | 337 | ||
| 338 | MAILDIR=$HOME/`mhparam Path` | 338 | MAILDIR=$HOME/`mhparam Path` |
| 339 | 339 | ||
| @@ -389,7 +389,7 @@ See `mh-bogofilter-blacklist' for more information." | |||
| 389 | SpamProbe is a Bayesian spam filtering program. Get it from your local | 389 | SpamProbe is a Bayesian spam filtering program. Get it from your local |
| 390 | distribution or from http://spamprobe.sourceforge.net. | 390 | distribution or from http://spamprobe.sourceforge.net. |
| 391 | 391 | ||
| 392 | To use SpamProbe, add the following recipes to `.procmailrc': | 392 | To use SpamProbe, add the following recipes to \".procmailrc\": |
| 393 | 393 | ||
| 394 | MAILDIR=$HOME/`mhparam Path` | 394 | MAILDIR=$HOME/`mhparam Path` |
| 395 | 395 | ||
diff --git a/lisp/mh-e/mh-mime.el b/lisp/mh-e/mh-mime.el index 5f7f81e7ac5..4338a94381b 100644 --- a/lisp/mh-e/mh-mime.el +++ b/lisp/mh-e/mh-mime.el | |||
| @@ -469,8 +469,8 @@ The effects of this command can be undone by running | |||
| 469 | (run-hooks 'mh-mh-to-mime-hook)) | 469 | (run-hooks 'mh-mh-to-mime-hook)) |
| 470 | 470 | ||
| 471 | (defun mh-mh-quote-unescaped-sharp () | 471 | (defun mh-mh-quote-unescaped-sharp () |
| 472 | "Quote `#' characters that haven't been quoted for \"mhbuild\". | 472 | "Quote \"#\" characters that haven't been quoted for \"mhbuild\". |
| 473 | If the `#' character is present in the first column, but it isn't | 473 | If the \"#\" character is present in the first column, but it isn't |
| 474 | part of a MH-style directive then \"mhbuild\" gives an error. | 474 | part of a MH-style directive then \"mhbuild\" gives an error. |
| 475 | This function will quote all such characters." | 475 | This function will quote all such characters." |
| 476 | (save-excursion | 476 | (save-excursion |
| @@ -604,7 +604,7 @@ media type if it cannot be determined automatically, a content | |||
| 604 | description and the DISPOSITION of the attachment. | 604 | description and the DISPOSITION of the attachment. |
| 605 | 605 | ||
| 606 | This is basically `mml-attach-file' from Gnus, modified such that a prefix | 606 | This is basically `mml-attach-file' from Gnus, modified such that a prefix |
| 607 | argument yields an `inline' disposition and Content-Type is determined | 607 | argument yields an \"inline\" disposition and Content-Type is determined |
| 608 | automatically." | 608 | automatically." |
| 609 | (let* ((file (mml-minibuffer-read-file "Attach file: ")) | 609 | (let* ((file (mml-minibuffer-read-file "Attach file: ")) |
| 610 | (type (mh-minibuffer-read-type file)) | 610 | (type (mh-minibuffer-read-type file)) |
diff --git a/lisp/mh-e/mh-pick.el b/lisp/mh-e/mh-pick.el index 02de9ff859a..03314ffa6c6 100644 --- a/lisp/mh-e/mh-pick.el +++ b/lisp/mh-e/mh-pick.el | |||
| @@ -224,7 +224,7 @@ The hook `mh-pick-mode-hook' is called upon entry to this mode. | |||
| 224 | 224 | ||
| 225 | Messages are searched for in the folder named in | 225 | Messages are searched for in the folder named in |
| 226 | `mh-searching-folder'. Add the messages found to the sequence | 226 | `mh-searching-folder'. Add the messages found to the sequence |
| 227 | named `search'." | 227 | named \"search\"." |
| 228 | (interactive) | 228 | (interactive) |
| 229 | (let ((pattern-list (mh-pick-parse-search-buffer)) | 229 | (let ((pattern-list (mh-pick-parse-search-buffer)) |
| 230 | (folder mh-searching-folder) | 230 | (folder mh-searching-folder) |
| @@ -337,9 +337,9 @@ COMPONENT is the component to search." | |||
| 337 | ;; All implementations of pick have special options -cc, -date, -from and | 337 | ;; All implementations of pick have special options -cc, -date, -from and |
| 338 | ;; -subject that allow to search for corresponding components. Any other | 338 | ;; -subject that allow to search for corresponding components. Any other |
| 339 | ;; component is searched using option --COMPNAME, for example: `pick | 339 | ;; component is searched using option --COMPNAME, for example: `pick |
| 340 | ;; --x-mailer mh-e'. Mailutils `pick' supports this option using a certain | 340 | ;; --x-mailer mh-e'. Mailutils "pick" supports this option using a certain |
| 341 | ;; kludge, but it prefers the following syntax for this purpose: | 341 | ;; kludge, but it prefers the following syntax for this purpose: |
| 342 | ;; `--component=COMPNAME --pattern=PATTERN'. | 342 | ;; "--component=COMPNAME --pattern=PATTERN". |
| 343 | ;; -- Sergey Poznyakoff, Aug 2003 | 343 | ;; -- Sergey Poznyakoff, Aug 2003 |
| 344 | (defun mh-pick-regexp-builder (pattern-list) | 344 | (defun mh-pick-regexp-builder (pattern-list) |
| 345 | "Generate pick search expression from PATTERN-LIST." | 345 | "Generate pick search expression from PATTERN-LIST." |
diff --git a/lisp/mh-e/mh-seq.el b/lisp/mh-e/mh-seq.el index 956115da7bb..6fb70e61de8 100644 --- a/lisp/mh-e/mh-seq.el +++ b/lisp/mh-e/mh-seq.el | |||
| @@ -282,7 +282,7 @@ When you want to widen the view to all your messages again, use | |||
| 282 | mh-show-seq-tool-bar-map)))) | 282 | mh-show-seq-tool-bar-map)))) |
| 283 | (push 'widen mh-view-ops))) | 283 | (push 'widen mh-view-ops))) |
| 284 | (t | 284 | (t |
| 285 | (error "No messages in sequence `%s'" (symbol-name sequence)))))) | 285 | (error "No messages in sequence \"%s\"" (symbol-name sequence)))))) |
| 286 | 286 | ||
| 287 | ;;;###mh-autoload | 287 | ;;;###mh-autoload |
| 288 | (defun mh-put-msg-in-seq (range sequence) | 288 | (defun mh-put-msg-in-seq (range sequence) |
| @@ -302,7 +302,7 @@ use." | |||
| 302 | (interactive (list (mh-interactive-range "Add messages from") | 302 | (interactive (list (mh-interactive-range "Add messages from") |
| 303 | (mh-read-seq-default "Add to" nil))) | 303 | (mh-read-seq-default "Add to" nil))) |
| 304 | (unless (mh-valid-seq-p sequence) | 304 | (unless (mh-valid-seq-p sequence) |
| 305 | (error "Can't put message in invalid sequence `%s'" sequence)) | 305 | (error "Can't put message in invalid sequence \"%s\"" sequence)) |
| 306 | (let* ((internal-seq-flag (mh-internal-seq sequence)) | 306 | (let* ((internal-seq-flag (mh-internal-seq sequence)) |
| 307 | (original-msgs (mh-seq-msgs (mh-find-seq sequence))) | 307 | (original-msgs (mh-seq-msgs (mh-find-seq sequence))) |
| 308 | (folders (list mh-current-folder)) | 308 | (folders (list mh-current-folder)) |
| @@ -428,7 +428,7 @@ containing the current message." | |||
| 428 | (t (intern input)))) | 428 | (t (intern input)))) |
| 429 | (msgs (mh-seq-to-msgs seq))) | 429 | (msgs (mh-seq-to-msgs seq))) |
| 430 | (if (and (null msgs) not-empty) | 430 | (if (and (null msgs) not-empty) |
| 431 | (error "No messages in sequence `%s'" seq)) | 431 | (error "No messages in sequence \"%s\"" seq)) |
| 432 | seq)) | 432 | seq)) |
| 433 | 433 | ||
| 434 | 434 | ||
| @@ -543,7 +543,7 @@ should be replaced with: | |||
| 543 | ((assoc (intern input) seq-list) | 543 | ((assoc (intern input) seq-list) |
| 544 | (cdr (assoc (intern input) seq-list))) | 544 | (cdr (assoc (intern input) seq-list))) |
| 545 | ((setq msg-list (mh-translate-range folder input)) msg-list) | 545 | ((setq msg-list (mh-translate-range folder input)) msg-list) |
| 546 | (t (error "No messages in range `%s'" input))))) | 546 | (t (error "No messages in range \"%s\"" input))))) |
| 547 | 547 | ||
| 548 | ;;;###mh-autoload | 548 | ;;;###mh-autoload |
| 549 | (defun mh-translate-range (folder expr) | 549 | (defun mh-translate-range (folder expr) |
| @@ -884,7 +884,7 @@ Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." | |||
| 884 | 884 | ||
| 885 | ;;;###mh-autoload | 885 | ;;;###mh-autoload |
| 886 | (defun mh-narrow-to-from (&optional pick-expr) | 886 | (defun mh-narrow-to-from (&optional pick-expr) |
| 887 | "Limit to messages with the same `From:' field. | 887 | "Limit to messages with the same \"From:\" field. |
| 888 | With a prefix argument, edit PICK-EXPR. | 888 | With a prefix argument, edit PICK-EXPR. |
| 889 | 889 | ||
| 890 | Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." | 890 | Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." |
| @@ -894,7 +894,7 @@ Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." | |||
| 894 | 894 | ||
| 895 | ;;;###mh-autoload | 895 | ;;;###mh-autoload |
| 896 | (defun mh-narrow-to-cc (&optional pick-expr) | 896 | (defun mh-narrow-to-cc (&optional pick-expr) |
| 897 | "Limit to messages with the same `Cc:' field. | 897 | "Limit to messages with the same \"Cc:\" field. |
| 898 | With a prefix argument, edit PICK-EXPR. | 898 | With a prefix argument, edit PICK-EXPR. |
| 899 | 899 | ||
| 900 | Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." | 900 | Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." |
| @@ -904,7 +904,7 @@ Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." | |||
| 904 | 904 | ||
| 905 | ;;;###mh-autoload | 905 | ;;;###mh-autoload |
| 906 | (defun mh-narrow-to-to (&optional pick-expr) | 906 | (defun mh-narrow-to-to (&optional pick-expr) |
| 907 | "Limit to messages with the same `To:' field. | 907 | "Limit to messages with the same \"To:\" field. |
| 908 | With a prefix argument, edit PICK-EXPR. | 908 | With a prefix argument, edit PICK-EXPR. |
| 909 | 909 | ||
| 910 | Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." | 910 | Use \\<mh-folder-mode-map>\\[mh-widen] to undo this command." |
diff --git a/lisp/mh-e/mh-utils.el b/lisp/mh-e/mh-utils.el index 6834f0d6d4b..ca51f59bc3f 100644 --- a/lisp/mh-e/mh-utils.el +++ b/lisp/mh-e/mh-utils.el | |||
| @@ -113,14 +113,14 @@ variable is only consulted if `mh-scan-format-file' is set to | |||
| 113 | (defvar mh-scan-msg-format-string "%d" | 113 | (defvar mh-scan-msg-format-string "%d" |
| 114 | "This is a format string for width of the message number in a scan format. | 114 | "This is a format string for width of the message number in a scan format. |
| 115 | 115 | ||
| 116 | Use `0%d' for zero-filled message numbers. This variable is only | 116 | Use \"0%d\" for zero-filled message numbers. This variable is only |
| 117 | consulted if `mh-scan-format-file' is set to \"Use MH-E scan | 117 | consulted if `mh-scan-format-file' is set to \"Use MH-E scan |
| 118 | Format\".") | 118 | Format\".") |
| 119 | 119 | ||
| 120 | (defvar mh-scan-msg-search-regexp "^[^0-9]*%d[^0-9]" | 120 | (defvar mh-scan-msg-search-regexp "^[^0-9]*%d[^0-9]" |
| 121 | "This regular expression matches a particular message. | 121 | "This regular expression matches a particular message. |
| 122 | 122 | ||
| 123 | It is a format string; use `%d' to represent the location of the | 123 | It is a format string; use \"%d\" to represent the location of the |
| 124 | message number within the expression as in the default of | 124 | message number within the expression as in the default of |
| 125 | \"^[^0-9]*%d[^0-9]\".") | 125 | \"^[^0-9]*%d[^0-9]\".") |
| 126 | 126 | ||
| @@ -137,7 +137,7 @@ Note that columns in Emacs start with 0.") | |||
| 137 | (defvar mh-note-seq ?% | 137 | (defvar mh-note-seq ?% |
| 138 | "Messages in a user-defined sequence are marked by this character. | 138 | "Messages in a user-defined sequence are marked by this character. |
| 139 | 139 | ||
| 140 | Messages in the `search' sequence are marked by this character as | 140 | Messages in the \"search\" sequence are marked by this character as |
| 141 | well.") | 141 | well.") |
| 142 | 142 | ||
| 143 | 143 | ||
| @@ -787,7 +787,7 @@ See `expand-file-name' for description of DEFAULT." | |||
| 787 | If the buffer we start in is still visible and DONT-RETURN is nil | 787 | If the buffer we start in is still visible and DONT-RETURN is nil |
| 788 | then switch to it after that." | 788 | then switch to it after that." |
| 789 | `(defun ,function () | 789 | `(defun ,function () |
| 790 | ,(format "Calls %s from the message's folder.\n%s\nSee `%s' for more info.\n" | 790 | ,(format "Calls %s from the message's folder.\n%s\nSee \"%s\" for more info.\n" |
| 791 | original-function | 791 | original-function |
| 792 | (if dont-return "" | 792 | (if dont-return "" |
| 793 | "When function completes, returns to the show buffer if it is | 793 | "When function completes, returns to the show buffer if it is |
| @@ -2107,7 +2107,7 @@ folder buffer are not updated." | |||
| 2107 | 2107 | ||
| 2108 | ;; Initialize mh-sub-folders-cache... | 2108 | ;; Initialize mh-sub-folders-cache... |
| 2109 | (defun mh-collect-folder-names () | 2109 | (defun mh-collect-folder-names () |
| 2110 | "Collect folder names by running `flists'." | 2110 | "Collect folder names by running \"flists\"." |
| 2111 | (unless mh-flists-process | 2111 | (unless mh-flists-process |
| 2112 | (setq mh-flists-process | 2112 | (setq mh-flists-process |
| 2113 | (mh-exec-cmd-daemon "folders" 'mh-collect-folder-names-filter | 2113 | (mh-exec-cmd-daemon "folders" 'mh-collect-folder-names-filter |