From: dick <dick.r.chiang@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: feature request: differentiate between read and automatically marked read
Date: Thu, 03 Feb 2022 07:26:20 -0500 [thread overview]
Message-ID: <87v8xw87bn.fsf@dick> (raw)
In-Reply-To: <87pmo41ghm.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 03 Feb 2022 08:50:13 +0000")
ESF> I use adaptive scoring and rely on it.
You'd be the first person or bot I've heard say this.
From Gnus Manual Section 8.6 "Initial impressions seem to indicate that
it's [i.e., adaptive scoring] totally useless as it stands."
Like most Gnus things, scoring is a bear to configure, but worse, its
default bag-of-words approach would get it wrong most of the time.
next prev parent reply other threads:[~2022-02-03 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 8:50 Eric S Fraga
2022-02-03 9:10 ` Eric S Fraga
2022-02-03 12:26 ` dick [this message]
2022-02-03 12:38 ` Tassilo Horn
2022-02-03 13:04 ` dick
2022-02-03 13:34 ` Eric S Fraga
2022-02-03 12:50 ` Eric S Fraga
2022-02-05 8:51 ` Uwe Brauer
2022-02-05 9:29 ` Eric S Fraga
2022-02-05 10:36 ` Uwe Brauer
2022-02-07 12:28 ` Eric S Fraga
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8xw87bn.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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.
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 NNTP newsgroup(s).