From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,INVALID_MSGID,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,
	RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 25934 invoked from network); 6 Oct 2023 03:22:42 -0000
Received: from mx1.math.uh.edu (129.7.128.32)
  by inbox.vuxu.org with ESMTPUTF8; 6 Oct 2023 03:22:42 -0000
Received: from lists1.math.uh.edu ([129.7.128.208])
	by mx1.math.uh.edu with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.96.1)
	(envelope-from <ding-owner+M39497=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1qobQ8-006EOU-1C
	for ml@inbox.vuxu.org;
	Thu, 05 Oct 2023 22:22:36 -0500
Received: from lists1.math.uh.edu ([127.0.0.1] helo=lists.math.uh.edu)
	by lists1.math.uh.edu with smtp (Exim 4.96)
	(envelope-from <ding-owner+M39497=ml=inbox.vuxu.org@lists.math.uh.edu>)
	id 1qobQ7-007P9n-2h
	for ml@inbox.vuxu.org;
	Thu, 05 Oct 2023 22:22:31 -0500
Received: from mx2.math.uh.edu ([129.7.128.33])
	by lists1.math.uh.edu with esmtp (Exim 4.96)
	(envelope-from <husain@alshehhi.io>)
	id 1qobQ5-007P9e-0x
	for ding@lists.math.uh.edu;
	Thu, 05 Oct 2023 22:22:29 -0500
Received: from quimby.gnus.org ([95.216.78.240])
	by mx2.math.uh.edu with esmtps  (TLS1.3) tls TLS_AES_256_GCM_SHA384
	(Exim 4.96.1)
	(envelope-from <husain@alshehhi.io>)
	id 1qobPv-000FP6-0H
	for ding@lists.math.uh.edu;
	Thu, 05 Oct 2023 22:22:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org;
	 s=20200322; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID
	:Subject:From:To:Date:Sender:Reply-To:Cc:Content-ID:Content-Description:
	Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:
	In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
	List-Post:List-Owner:List-Archive;
	bh=XU82nAPARp2MAZCJNqyXbSV6TgmV5OS6YK/ChD4BlX4=; b=dYR6hjsqW3mXS2G+03qCDd7uDd
	RGa8KMtMJlDSFMRIRMSk4nSzfLN5b8ll83yEtogHj2+xhaBjiPMYjdIonY21EWnhcdX2wtecUgH8g
	csEUJFlvXGUZ8/tbL6DH0b1d2GjUrstJzVyDl01q3i32q0YHQH/SHflK5QL7AZHel3j0=;
Received: from mail-4022.proton.ch ([185.70.40.22])
	by quimby.gnus.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <husain@alshehhi.io>)
	id 1qobPi-0008MI-Ug
	for ding@gnus.org; Fri, 06 Oct 2023 05:22:13 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alshehhi.io;
	s=protonmail3; t=1696562524; x=1696821724;
	bh=XU82nAPARp2MAZCJNqyXbSV6TgmV5OS6YK/ChD4BlX4=;
	h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date:
	 Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector;
	b=SjeT/9CZG41YRs2zq6tWZ1psZh8sfXST3J+OtJpsobL76OuLHokQm5SqgkZGJsTLY
	 YaJ8PhEIWZkJ3x8GIjKmQCVvgeSpV/bQZ1792lwuXR2lWsbcU+OFR3a3T3IaMVSzjC
	 y6h1T48MrKJc4QnFKVchNf2vZhIkq7A8rvAivoIgcc6IYa3vaRwaTref0z64Nc8LXr
	 dZLVmQNjCeBYddebbX4Q29uLtUtwtOZkO+eg59+cXKuGt571oBuVPwkvVR4QRMVvPg
	 U1yqtQQwUypACSdkjd04dIqo7oxsyp8YVG+M8mSk7y5rLdz0PjFz/LW6OmGfERs9tz
	 7OYTWx/I6gbJA==
Date: Fri, 06 Oct 2023 03:22:00 +0000
To: ding@gnus.org
From: husain@alshehhi.io
Subject: Adaptive scoring is enabled but does not take effect
Message-ID: <87edi8mo4q.fsf@>
Feedback-ID: 31127354:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-ID: <ding.gnus.org>
Precedence: bulk


I am using adaptive scoring. In the gnus-summary buffer, I see that
gnus-use-scoring is set to t, and gnus-use-adaptive-scoring is also set
to t. Also, the value of gnus-default-adaptive-score-alist is

((gnus-kill-file-mark)
 (gnus-unread-mark)
 (gnus-read-mark
  (from 5)
  (subject 30))
 (gnus-catchup-mark
  (subject -10))
 (gnus-killed-mark
  (from -4)
  (subject -20))
 (gnus-del-mark
  (from -4)
  (subject -15)))

Yet, when I go read or catchup or kill, that does not seem to affect the
score that I have displayed in the summary buffer. I existed gnus and
opened it again with no change. Looks like it is not turned on, but
given the documentation, it should be turned on.

Any help debugging this issue is appreciated.