Gnus development mailing list
 help / color / mirror / Atom feed
From: Hans de Graaff <J.J.deGraaff@twi.tudelft.nl>
Subject: Re: Adaptive scoring in nnml groups
Date: 10 Oct 1996 15:43:25 +0200	[thread overview]
Message-ID: <yah4tk3ylxd.fsf@twi.tudelft.nl> (raw)
In-Reply-To: Wesley.Hardaker@sphys.unil.ch's message of 02 Oct 1996 14:14:16 +0100

It seems I'm starting to understand what has been happening here.

Wesley.Hardaker@sphys.unil.ch writes:

> Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> 
> > Hm...  I couldn't find anything in the adaptive score code that would
> > make adaptive scoring be switched on only in nntp groups.  Are you
> > sure you're not switching it off in some hook or other?

Adaptive scoring was on for those groups.

> I don't know if you rememeber or not, but I have been having this
> exact same problem for a long time now.  I turned on adaptive
> scoring way back in .20 or so of sgnus and starting using nnml later
> on.  I wrote to you and told you about this problem, and you said
> something to the effect of 'I can't repeat it using your settings',
> so I figured I must be doing something wierd.

Probably the weird thing is that you are using something like 

    (setq gnus-auto-expirable-newsgroups "mail\\..*")

I just turned this off, and lo and behold: ADAPT files for my nnml
groups. What seems to happen is that all articles get another mark
because of this, and this mark isn't in the adaptive alist. If there
are no scores, the cache data isn't 'touched, and no ADAPT file gets
written.

In addition to this I was ticking other articles, and there is no
default adaptive alist rule for gnus-ticked-mark articles. So, again,
no scores.

Lars, I hope this pins this down a bit more. It seems to be the marks
should be run through adaptive scoring first, before auto-expriable
gets its hands on them and changes them to gnus-expirable-mark.
Otherwise I suppose I should switch to total-expire, but in that case
a warning about this on the Expiring Mail page of the info file would
be nice.

Hans


  parent reply	other threads:[~1996-10-10 13:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-01 14:48 Hans de Graaff
1996-10-01 16:47 ` Richard Pieri
1996-10-02  0:05 ` Lars Magne Ingebrigtsen
1996-10-02  7:49   ` Hans de Graaff
1996-10-02 13:14   ` Wesley.Hardaker
1996-10-02 20:46     ` Steven L Baur
1996-10-04  6:40     ` Lars Magne Ingebrigtsen
1996-10-04  6:53       ` Wesley.Hardaker
1996-10-08  8:42     ` Hans de Graaff
1996-10-10 22:15       ` Lars Magne Ingebrigtsen
1996-10-10 13:43     ` Hans de Graaff [this message]
1996-10-11  6:40       ` Wesley.Hardaker
1996-10-11 10:39       ` Lars Magne Ingebrigtsen
1996-10-11 13:04         ` Wesley.Hardaker
1996-10-11 13:13           ` Lars Magne Ingebrigtsen
1996-10-11 14:32             ` Wesley.Hardaker
1996-10-11 14:57             ` Hans de Graaff
1996-10-12 18:47               ` Lars Magne Ingebrigtsen
1996-10-13  7:07             ` Yair Friedman
1996-10-14 20:12               ` Lars Magne Ingebrigtsen

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=yah4tk3ylxd.fsf@twi.tudelft.nl \
    --to=j.j.degraaff@twi.tudelft.nl \
    /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).