# HG changeset patch # User Bill Wohler # Date 1130723991 0 # Node ID a99155be4d044f54945c80be7f64aa75753779ce # Parent beb6b92a94f67cdcde1222c9f32bb6f84134b68f (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. diff -r beb6b92a94f6 -r a99155be4d04 lisp/mh-e/ChangeLog --- a/lisp/mh-e/ChangeLog Mon Oct 31 01:37:30 2005 +0000 +++ b/lisp/mh-e/ChangeLog Mon Oct 31 01:59:51 2005 +0000 @@ -1,5 +1,9 @@ 2005-10-30 Bill Wohler + * mh-e.el (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. + * mh-customize.el (mh-compose-space-does-completion-flag) (mh-signature-separator-flag, mh-interpret-number-as-range-flag) (mh-adaptive-cmd-note-flag): Use "Non-nil means" instead of "On diff -r beb6b92a94f6 -r a99155be4d04 lisp/mh-e/mh-e.el --- a/lisp/mh-e/mh-e.el Mon Oct 31 01:37:30 2005 +0000 +++ b/lisp/mh-e/mh-e.el Mon Oct 31 01:59:51 2005 +0000 @@ -184,24 +184,30 @@ It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the message number as in the default of -\"^\\\\( *[0-9]+\\\\)[^D^0-9]\". This regular expression should be correct as -it is needed by non-fontifying functions.") +\"^\\\\( *[0-9]+\\\\)[^D^0-9]\". This expression includes the leading space +within the parenthesis since it looks better to highlight it as well. This +regular expression should be correct as it is needed by non-fontifying +functions.") (defvar mh-scan-deleted-msg-regexp "^\\( *[0-9]+\\)D" "This regular expression matches deleted messages. It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the message number as in the default of -\"^\\\\( *[0-9]+\\\\)D\". This regular expression should be correct as it is -needed by non-fontifying functions. See also `mh-note-deleted'.") +\"^\\\\( *[0-9]+\\\\)D\". This expression includes the leading space within +the parenthesis since it looks better to highlight it as well. This regular +expression should be correct as it is needed by non-fontifying functions. See +also `mh-note-deleted'.") (defvar mh-scan-refiled-msg-regexp "^\\( *[0-9]+\\)\\^" "This regular expression matches refiled messages. It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the message number as in the default of -\"^\\\\( *[0-9]+\\\\)\\\\^\". This regular expression should be correct as it -is needed by non-fontifying functions. See also `mh-note-refiled'.") +\"^\\\\( *[0-9]+\\\\)\\\\^\". This expression includes the leading space +within the parenthesis since it looks better to highlight it as well. This +regular expression should be correct as it is needed by non-fontifying +functions. See also `mh-note-refiled'.") (defvar mh-scan-valid-regexp "^ *[0-9]" "This regular expression describes a valid scan line. @@ -213,8 +219,10 @@ It must match from the beginning of the line. Note that the default setting of `mh-folder-font-lock-keywords' expects this expression to contain at least one parenthesized expression which matches the message number as in the default of -\"^\\\\( *[0-9]+\\\\+\\\\).*\". This regular expression should be correct as -it is needed by non-fontifying functions. See also `mh-note-cur'.") +\"^\\\\( *[0-9]+\\\\+\\\\).*\". This expression includes the leading space and +current message marker \"+\" within the parenthesis since it looks better to +highlight these items as well. This regular expression should be correct as it +is needed by non-fontifying functions. See also `mh-note-cur'.") (defvar mh-scan-date-regexp "\\([0-9][0-9]/[0-9][0-9]\\)" "This regular expression matches a valid date.