Gnus: Permanently killing a thread?

Gnus: Permanently killing a thread?

[Christopher Howard]

Hi, in Gnus I frequently use gnus-summary-kill-same-subject (C-k) to kill threads that are of no interest to me. However, when I am reading news the next day, I have to deal again with new messages from that thread. I'm wondering if I have a mechanism in Gnus to permanently hide a thread.

In the manual, am seeing a lot of information about thread scoring, but I'm not sure if/how that is something I can leverage toward this end.

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

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

Re: Gnus: Permanently killing a thread?

[Robert Pluim]

>>>>> On Wed, 11 Dec 2024 07:52:38 -0900, Christopher Howard <christopher@librehacker.com> said:

    Christopher> Hi, in Gnus I frequently use gnus-summary-kill-same-subject (C-k) to
    Christopher> kill threads that are of no interest to me. However, when I am reading
    Christopher> news the next day, I have to deal again with new messages from that
    Christopher> thread. I'm wondering if I have a mechanism in Gnus to permanently
    Christopher> hide a thread.

C-k only applies to the current summary. What youʼre looking for is
traditionally a kill file, accessible via 'M-k'. However..

    Christopher> In the manual, am seeing a lot of information about
    Christopher> thread scoring, but I'm not sure if/how that is
    Christopher> something I can leverage toward this end.

..kill files are allegedly slow. So what you do instead is 'L', which
allows you to lower the score of a thread, and then you can use 'V x'
to set the score below which messages are automatically hidden (I
donʼt remember offhand if the effect of 'V x' is permanent or not, as
I donʼt really use scoring).

Robert
-- 

Re: Gnus: Permanently killing a thread?

[Christopher Howard]

Robert Pluim <rpluim@gmail.com> writes:

> ..kill files are allegedly slow. So what you do instead is 'L', which
> allows you to lower the score of a thread, and then you can use 'V x'
> to set the score below which messages are automatically hidden (I
> donʼt remember offhand if the effect of 'V x' is permanent or not, as
> I donʼt really use scoring).

The score approaches sounds find, except I was just wondering: Is the score somehow portable across multiple computers? I use multiple backends, including nnimap, nnatom, nnrss, and nntp. However, focusing on the IMAP messages, it seems that if I mark a message as read (which I think is basically the same thing as "killing" it) then the message is still marked as read when I login via Gnus on a different computer. Would hiding still work if I was just marking messages with a low score?

I only use nnatom, nnrss, and nntp on one computer, but the nnimap, including the mailing list groups, are used from both computers.

-- 
Christopher Howard

Re: Gnus: Permanently killing a thread?

[Greg Farough]

On Wed, Dec 11 2024, Christopher Howard <christopher@librehacker.com> wrote:

> Robert Pluim <rpluim@gmail.com> writes:
>
>> ..kill files are allegedly slow. So what you do instead is 'L', which
>> allows you to lower the score of a thread, and then you can use 'V x'
>> to set the score below which messages are automatically hidden (I
>> donʼt remember offhand if the effect of 'V x' is permanent or not, as
>> I donʼt really use scoring).
>
> The score approaches sounds find, except I was just wondering: Is the
> score somehow portable across multiple computers? I use multiple
> backends, including nnimap, nnatom, nnrss, and nntp. However, focusing
> on the IMAP messages, it seems that if I mark a message as read (which
> I think is basically the same thing as "killing" it) then the message
> is still marked as read when I login via Gnus on a different computer.
> Would hiding still work if I was just marking messages with a low
> score?
>
> I only use nnatom, nnrss, and nntp on one computer, but the nnimap,
> including the mailing list groups, are used from both computers.

I personally sync my score file across computers through Syncthing.

-g

-- 
"I want the freedom and the Guile."

Re: Gnus: Permanently killing a thread?

[Joel Reicher]

Christopher Howard <christopher@librehacker.com> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>
>> ..kill files are allegedly slow. So what you do instead is 'L', 
>> which allows you to lower the score of a thread, and then you 
>> can use 'V x' to set the score below which messages are 
>> automatically hidden (I donʼt remember offhand if the effect of 
>> 'V x' is permanent or not, as I donʼt really use scoring).
>
> The score approaches sounds find, except I was just wondering: 
> Is the score somehow portable across multiple computers? I use 
> multiple backends, including nnimap, nnatom, nnrss, and 
> nntp. However, focusing on the IMAP messages, it seems that if I 
> mark a message as read (which I think is basically the same 
> thing as "killing" it) then the message is still marked as read 
> when I login via Gnus on a different computer. Would hiding 
> still work if I was just marking messages with a low score?
>
> I only use nnatom, nnrss, and nntp on one computer, but the 
> nnimap, including the mailing list groups, are used from both 
> computers.

IMAP is a bit of a special case; where possible (always, perhaps?) 
Gnus will use IMAP flags stored on the server for representing 
things like readedness marks, ticks, etc.

It's also hiding read messages in the default view, right?

Cheers,

        - Joel

Re: Gnus: Permanently killing a thread?

[Christopher Howard]

Joel Reicher <joel.reicher@gmail.com> writes:

> IMAP is a bit of a special case; where possible (always, perhaps?)
> Gnus will use IMAP flags stored on the server for representing things
> like readedness marks, ticks, etc.

I'm working through the manual sections on scoring, and it says that messages below a certain score threshold are marked as read. So I think that would take care of the concern I have, since it appears that (somehow or other) messages marked "read" are also marked as such on the IMAP server itself. The default score threshold is 0, so presumably it must be possible to give something a negative score.

-- 
Christopher Howard

Re: Gnus: Permanently killing a thread?

[Joel Reicher]

Christopher Howard <christopher@librehacker.com> writes:

> Joel Reicher <joel.reicher@gmail.com> writes:
>
>> IMAP is a bit of a special case; where possible (always, 
>> perhaps?)  Gnus will use IMAP flags stored on the server for 
>> representing things like readedness marks, ticks, etc.
>
> I'm working through the manual sections on scoring, and it says 
> that messages below a certain score threshold are marked as 
> read. So I think that would take care of the concern I have, 
> since it appears that (somehow or other) messages marked "read" 
> are also marked as such on the IMAP server itself. The default 
> score threshold is 0, so presumably it must be possible to give 
> something a negative score.

I think you're right. My understanding is that scoring is "before" 
readedness. Once an IMAP article is marked as read (whether by 
score processing or anything else) Gnus will store that readedness 
mark on the server as part of normal IMAP support, same as many 
other marks for an IMAP article.

Regards,

        - Joel

Re: Gnus: Permanently killing a thread?

[Björn Bidar]

Joel Reicher <joel.reicher@gmail.com> writes:

> Christopher Howard <christopher@librehacker.com> writes:
>
>> Robert Pluim <rpluim@gmail.com> writes:
>>
>>> ..kill files are allegedly slow. So what you do instead is 'L',
>>> which allows you to lower the score of a thread, and then you can
>>> use 'V x' to set the score below which messages are automatically
>>> hidden (I donʼt remember offhand if the effect of 'V x' is
>>> permanent or not, as I donʼt really use scoring).
>>
>> The score approaches sounds find, except I was just wondering: Is
>> the score somehow portable across multiple computers? I use multiple
>> backends, including nnimap, nnatom, nnrss, and nntp. However,
>> focusing on the IMAP messages, it seems that if I mark a message as
>> read (which I think is basically the same thing as "killing" it)
>> then the message is still marked as read when I login via Gnus on a
>> different computer. Would hiding still work if I was just marking
>> messages with a low score?
>>
>> I only use nnatom, nnrss, and nntp on one computer, but the nnimap,
>> including the mailing list groups, are used from both computers.
>
> IMAP is a bit of a special case; where possible (always, perhaps?)
> Gnus will use IMAP flags stored on the server for representing things
> like readedness marks, ticks, etc.
>

It could do that but doesn't at the moment. Nnimap Gnus IMAP backend
can already query capabilities. If it implements rfc5464 IMAP METADATA it could be
possible to store these inside the metadata of severs which support the
extension.

Re: Gnus: Permanently killing a thread?

[Joel Reicher]

Björn Bidar <bjorn.bidar@thaodan.de> writes:

> Joel Reicher <joel.reicher@gmail.com> writes:
>
>> IMAP is a bit of a special case; where possible (always, 
>> perhaps?)  Gnus will use IMAP flags stored on the server for 
>> representing things like readedness marks, ticks, etc.
>
> It could do that but doesn't at the moment. Nnimap Gnus IMAP 
> backend can already query capabilities. If it implements rfc5464 
> IMAP METADATA it could be possible to store these inside the 
> metadata of severs which support the extension.

OK, so just seen, flagged, and answered? (That's what I can see in 
nnimap-mark-alist; should have looked earlier)

Regards,

        - Joel

Re: Gnus: Permanently killing a thread?

[Manuel Giraud via Users list for the GNU Emacs text editor]

Christopher Howard <christopher@librehacker.com> writes:

[...]

> In the manual, am seeing a lot of information about thread scoring,
> but I'm not sure if/how that is something I can leverage toward this
> end.

I think this is the way to go.  There is also a (configurable) score
level and Gnus will hide post/mail that have a score below this level.
-- 
Manuel Giraud