From: "Štěpán Němec" <stepnem@gmail.com>
To: 39780@debbugs.gnu.org
Subject: bug#39780: [PATCH] Mention 'spam-stat-process-directory-age' in the documentation
Date: Sat, 18 Apr 2020 13:51:55 +0200 [thread overview]
Message-ID: <87r1wl6mg4.fsf@gmail.com> (raw)
In-Reply-To: <20200225125812.1221377-1-stepnem@gmail.com> ("Štěpán Němec"'s message of "Tue, 25 Feb 2020 13:58:12 +0100")
On Tue, 25 Feb 2020 13:58:12 +0100
Štěpán Němec wrote:
> I was at a loss as to why my attempt to set up spam-stat seemed to
> have no effect, only to find (digging in the code) that it was
> ignoring most of the sample files due to this undocumented variable.
>
> * doc/misc/gnus.texi (Creating a spam-stat dictionary): Document
> the variable 'spam-stat-process-directory-age'.
> ---
> doc/misc/gnus.texi | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
> index 424e15bc6d..718e269fc8 100644
> --- a/doc/misc/gnus.texi
> +++ b/doc/misc/gnus.texi
> @@ -25668,6 +25668,13 @@ Creating a spam-stat dictionary
> file is treated as one non-spam mail.
> @end defun
>
> +@defvar spam-stat-process-directory-age
> +Maximum age of files to be processed, in days. Without this filter,
> +re-training spam-stat with several thousand messages could take a long
> +time. The default is 90, but you might want to set this to a bigger
> +value during the initial training.
> +@end defvar
> +
> Usually you would call @code{spam-stat-process-spam-directory} on a
> directory such as @file{~/Mail/mail/spam} (this usually corresponds to
> the group @samp{nnml:mail.spam}), and you would call
Any reason not to include this in emacs-27?
--
Štěpán
next prev parent reply other threads:[~2020-04-18 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 12:58 bug#39780: [PATCH] Mention 'spam-stat-process-directory-age' in the documentation Štěpán Němec
2020-04-18 11:51 ` Štěpán Němec [this message]
2020-04-18 12:29 ` Eli Zaretskii
2020-04-18 15:19 ` Štěpán Němec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1wl6mg4.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=39780@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).