From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: feature request: differentiate between read and automatically marked read
Date: Thu, 03 Feb 2022 12:50:14 +0000 [thread overview]
Message-ID: <87mtj85d2x.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87v8xw87bn.fsf@dick>
On Thursday, 3 Feb 2022 at 07:26, dick wrote:
> You'd be the first person or bot I've heard say this.
I've never been called a bot before. :-)
> 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.
Well, it works for me. Yes, I spent some time getting the weights right
for the various actions used for scoring but, at the very least, it does
sort my emails in order of decreasing relevance/importance most of the
time. And it does a good job of automatically marking as read emails
that I am seldom going to read.
Also works well for some of the newsgroups (e.g. emacs.help and
emacs.devel) and some rss feeds (arxiv).
For the record, my settings are:
#+begin_src emacs-lisp
(setq gnus-default-adaptive-score-alist
'(;(gnus-kill-file-mark)
;;(gnus-unread-mark)
;; (gnus-read-mark (from 5) (subject 30))
(gnus-replied-mark (from 50) (subject 10))
(gnus-read-mark (from 30) (subject 10))
(gnus-cached-mark (from 30) (subject 10))
(gnus-forwarded-mark (from 10) (subject 5))
(gnus-saved-mark (from 10) (subject 5))
(gnus-expirable-mark (from 0) (subject 0))
(gnus-catchup-mark (from -5) (subject -30))
(gnus-killed-mark (subject -100))
(gnus-del-mark (from -10) (subject -50)))
gnus-default-adaptive-word-score-alist '((42 . 3) ;cached
(65 . 2) ;replied
(70 . 1) ;forwarded
(82 . 1) ;read
(67 . -1) ;catchup
(69 . 0) ;expired
(75 . -3) ;killed
(114 . -3)) ;deleted
)
#+end_src
and I've been using these now for a few years.
I should add that I do have some fixed scores as well so, for instance,
emails to me from the PhD students I supervise always score high no
matter what the subject is.
--
Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.2
next prev parent reply other threads:[~2022-02-03 12:50 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
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 [this message]
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=87mtj85d2x.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.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.
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).