diff options
| author | Bill Wohler | 2005-10-31 01:59:51 +0000 |
|---|---|---|
| committer | Bill Wohler | 2005-10-31 01:59:51 +0000 |
| commit | ece9cbf7d88c3390e7e2380887b77899d9afaf20 (patch) | |
| tree | df70c5bca2b446fa9a8bc80872af1941bc64dc57 | |
| parent | fefc50792516b7bd3b96a49f333cdfa1e09a2c75 (diff) | |
| download | emacs-ece9cbf7d88c3390e7e2380887b77899d9afaf20.tar.gz emacs-ece9cbf7d88c3390e7e2380887b77899d9afaf20.zip | |
(mh-scan-good-msg-regexp, mh-scan-deleted-msg-regexp)
(mh-scan-refiled-msg-regexp, mh-scan-cur-msg-number-regexp): Sync
docstrings with manual.
| -rw-r--r-- | lisp/mh-e/ChangeLog | 4 | ||||
| -rw-r--r-- | lisp/mh-e/mh-e.el | 24 |
2 files changed, 20 insertions, 8 deletions
diff --git a/lisp/mh-e/ChangeLog b/lisp/mh-e/ChangeLog index 449c291e96c..13d87f794e4 100644 --- a/lisp/mh-e/ChangeLog +++ b/lisp/mh-e/ChangeLog | |||
| @@ -1,5 +1,9 @@ | |||
| 1 | 2005-10-30 Bill Wohler <wohler@newt.com> | 1 | 2005-10-30 Bill Wohler <wohler@newt.com> |
| 2 | 2 | ||
| 3 | * mh-e.el (mh-scan-good-msg-regexp, mh-scan-deleted-msg-regexp) | ||
| 4 | (mh-scan-refiled-msg-regexp, mh-scan-cur-msg-number-regexp): Sync | ||
| 5 | docstrings with manual. | ||
| 6 | |||
| 3 | * mh-customize.el (mh-compose-space-does-completion-flag) | 7 | * mh-customize.el (mh-compose-space-does-completion-flag) |
| 4 | (mh-signature-separator-flag, mh-interpret-number-as-range-flag) | 8 | (mh-signature-separator-flag, mh-interpret-number-as-range-flag) |
| 5 | (mh-adaptive-cmd-note-flag): Use "Non-nil means" instead of "On | 9 | (mh-adaptive-cmd-note-flag): Use "Non-nil means" instead of "On |
diff --git a/lisp/mh-e/mh-e.el b/lisp/mh-e/mh-e.el index dc67cce51c5..7f022687aef 100644 --- a/lisp/mh-e/mh-e.el +++ b/lisp/mh-e/mh-e.el | |||
| @@ -184,24 +184,30 @@ See also `mh-scan-cur-msg-number-regexp'.") | |||
| 184 | It must match from the beginning of the line. Note that the default setting of | 184 | It must match from the beginning of the line. Note that the default setting of |
| 185 | `mh-folder-font-lock-keywords' expects this expression to contain at least one | 185 | `mh-folder-font-lock-keywords' expects this expression to contain at least one |
| 186 | parenthesized expression which matches the message number as in the default of | 186 | parenthesized expression which matches the message number as in the default of |
| 187 | \"^\\\\( *[0-9]+\\\\)[^D^0-9]\". This regular expression should be correct as | 187 | \"^\\\\( *[0-9]+\\\\)[^D^0-9]\". This expression includes the leading space |
| 188 | it is needed by non-fontifying functions.") | 188 | within the parenthesis since it looks better to highlight it as well. This |
| 189 | regular expression should be correct as it is needed by non-fontifying | ||
| 190 | functions.") | ||
| 189 | 191 | ||
| 190 | (defvar mh-scan-deleted-msg-regexp "^\\( *[0-9]+\\)D" | 192 | (defvar mh-scan-deleted-msg-regexp "^\\( *[0-9]+\\)D" |
| 191 | "This regular expression matches deleted messages. | 193 | "This regular expression matches deleted messages. |
| 192 | It must match from the beginning of the line. Note that the default setting of | 194 | It must match from the beginning of the line. Note that the default setting of |
| 193 | `mh-folder-font-lock-keywords' expects this expression to contain at least one | 195 | `mh-folder-font-lock-keywords' expects this expression to contain at least one |
| 194 | parenthesized expression which matches the message number as in the default of | 196 | parenthesized expression which matches the message number as in the default of |
| 195 | \"^\\\\( *[0-9]+\\\\)D\". This regular expression should be correct as it is | 197 | \"^\\\\( *[0-9]+\\\\)D\". This expression includes the leading space within |
| 196 | needed by non-fontifying functions. See also `mh-note-deleted'.") | 198 | the parenthesis since it looks better to highlight it as well. This regular |
| 199 | expression should be correct as it is needed by non-fontifying functions. See | ||
| 200 | also `mh-note-deleted'.") | ||
| 197 | 201 | ||
| 198 | (defvar mh-scan-refiled-msg-regexp "^\\( *[0-9]+\\)\\^" | 202 | (defvar mh-scan-refiled-msg-regexp "^\\( *[0-9]+\\)\\^" |
| 199 | "This regular expression matches refiled messages. | 203 | "This regular expression matches refiled messages. |
| 200 | It must match from the beginning of the line. Note that the default setting of | 204 | It must match from the beginning of the line. Note that the default setting of |
| 201 | `mh-folder-font-lock-keywords' expects this expression to contain at least one | 205 | `mh-folder-font-lock-keywords' expects this expression to contain at least one |
| 202 | parenthesized expression which matches the message number as in the default of | 206 | parenthesized expression which matches the message number as in the default of |
| 203 | \"^\\\\( *[0-9]+\\\\)\\\\^\". This regular expression should be correct as it | 207 | \"^\\\\( *[0-9]+\\\\)\\\\^\". This expression includes the leading space |
| 204 | is needed by non-fontifying functions. See also `mh-note-refiled'.") | 208 | within the parenthesis since it looks better to highlight it as well. This |
| 209 | regular expression should be correct as it is needed by non-fontifying | ||
| 210 | functions. See also `mh-note-refiled'.") | ||
| 205 | 211 | ||
| 206 | (defvar mh-scan-valid-regexp "^ *[0-9]" | 212 | (defvar mh-scan-valid-regexp "^ *[0-9]" |
| 207 | "This regular expression describes a valid scan line. | 213 | "This regular expression describes a valid scan line. |
| @@ -213,8 +219,10 @@ This is used to eliminate error messages that are occasionally produced by | |||
| 213 | It must match from the beginning of the line. Note that the default setting of | 219 | It must match from the beginning of the line. Note that the default setting of |
| 214 | `mh-folder-font-lock-keywords' expects this expression to contain at least one | 220 | `mh-folder-font-lock-keywords' expects this expression to contain at least one |
| 215 | parenthesized expression which matches the message number as in the default of | 221 | parenthesized expression which matches the message number as in the default of |
| 216 | \"^\\\\( *[0-9]+\\\\+\\\\).*\". This regular expression should be correct as | 222 | \"^\\\\( *[0-9]+\\\\+\\\\).*\". This expression includes the leading space and |
| 217 | it is needed by non-fontifying functions. See also `mh-note-cur'.") | 223 | current message marker \"+\" within the parenthesis since it looks better to |
| 224 | highlight these items as well. This regular expression should be correct as it | ||
| 225 | is needed by non-fontifying functions. See also `mh-note-cur'.") | ||
| 218 | 226 | ||
| 219 | (defvar mh-scan-date-regexp "\\([0-9][0-9]/[0-9][0-9]\\)" | 227 | (defvar mh-scan-date-regexp "\\([0-9][0-9]/[0-9][0-9]\\)" |
| 220 | "This regular expression matches a valid date. | 228 | "This regular expression matches a valid date. |