Gnus: Lowering thread score

Gnus: Lowering thread score

[Christopher Howard]

Hi. In my mailing list Gnus groups, I have been using gnus-summary-lower-score to hide uninteresting threads. More specifically, I have been using "L s e t <return>" (in a macro), to lower score by subject, and this has been working pretty well in practice. However, it occurred to me this later on my potentially hide threads that are a different thread, but the same subject. That could be a problem if, say, a year from now I decide that the subject is now interesting, or if somebody uses a short, ambiguous subject line.

I tried replacing this with "L t e t <return>" but that does not appear to be working — none of the thread messages get marked as "Y" or anything, as far as I can tell. Could somebody give me some guidance on this?

-- 
📛 Christopher Howard
🚀 gemini://gem.librehacker.com
🌐 http://gem.librehacker.com

בראשית ברא אלהים את השמים ואת הארץ

Re: Gnus: Lowering thread score

[James Thomas]

(I haven't used all this in a while; this is just based on the manual)

Christopher Howard wrote:

> Hi. In my mailing list Gnus groups, I have been using
> gnus-summary-lower-score to hide uninteresting threads. More
> specifically, I have been using "L s e t <return>" (in a macro), to
> lower score by subject, and this has been working pretty well in
> practice. However, it occurred to me this later on my potentially hide
> threads that are a different thread, but the same subject. That could
> be a problem if, say, a year from now I decide that the subject is now
> interesting, or if somebody uses a short, ambiguous subject line.

Aren't you using a temporary entry anyway?

> I tried replacing this with "L t e t <return>" but that does not
> appear to be working — none of the thread messages get marked as "Y"
> or anything, as far as I can tell. Could somebody give me some
> guidance on this?

I hope you understand correctly that that's only for a _particular
thread_; anyway check the conditions mentioned in “Thread” in (info
"(gnus) Score File Format").

--

Re: Gnus: Lowering thread score

[Christopher Howard]

James Thomas <jimjoe@gmx.net> writes:

> Aren't you using a temporary entry anyway?

True, yes, I hadn't been thinking about that.

I'm curious now about what actually controls the expiration time. The manual is a little vague:

```
There are two sorts of scoring entries: Permanent and temporary.
Temporary score entries are self-expiring entries.  Any entries that are
temporary and have not been used for, say, a week, will be removed
silently to help keep the sizes of the score files down.
```

So, is "a week" the hardcoded time limit, or is that just an example amount, and some variable controls it?

>
>> I tried replacing this with "L t e t <return>" but that does not
>> appear to be working — none of the thread messages get marked as "Y"
>> or anything, as far as I can tell. Could somebody give me some
>> guidance on this?
>
> I hope you understand correctly that that's only for a _particular
> thread_; anyway check the conditions mentioned in “Thread” in (info
> "(gnus) Score File Format").

Thanks, I looked at that just now. It is not clear to me, based on that, why I don't see the expected result when trying to apply the thread match to any arbitrary (sub) thread. But maybe I just don't really understand how threads are tracked in e-mail.

-- 
Christopher Howard

Re: Gnus: Lowering thread score

[James Thomas]

Christopher Howard <christopher@librehacker.com> writes:

> James Thomas <jimjoe@gmx.net> writes:
>
>> Aren't you using a temporary entry anyway?
>
> True, yes, I hadn't been thinking about that.
>
> I'm curious now about what actually controls the expiration time. The
> manual is a little vague:
>
> ```
> There are two sorts of scoring entries: Permanent and temporary.
> Temporary score entries are self-expiring entries.  Any entries that are
> temporary and have not been used for, say, a week, will be removed
> silently to help keep the sizes of the score files down.
> ```
>
> So, is "a week" the hardcoded time limit, or is that just an example
> amount, and some variable controls it?

Usually when it's vague so, there's a mention somewhere else: try
gnus-score-expiry-days in (info "(gnus) Score Variables").

>>> I tried replacing this with "L t e t <return>" but that does not
>>> appear to be working — none of the thread messages get marked as "Y"
>>> or anything, as far as I can tell. Could somebody give me some
>>> guidance on this?
>>
>> I hope you understand correctly that that's only for a _particular
>> thread_; anyway check the conditions mentioned in “Thread” in (info
>> "(gnus) Score File Format").
>
> Thanks, I looked at that just now. It is not clear to me, based on
> that, why I don't see the expected result when trying to apply the
> thread match to any arbitrary (sub) thread. But maybe I just don't
> really understand how threads are tracked in e-mail.

Check the actual score as well: perhaps it's not yet below 0.

--