From: Mark Plaksin <happy@mcplaksin.org>
Subject: Re: CODE: Hide groups with few unread articles
Date: Sun, 16 Apr 2006 16:27:35 -0400 [thread overview]
Message-ID: <wsbqv1s1u0.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <m3fykg89w0.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Mark Plaksin <happy@usg.edu> writes:
>
>> You get a new group parameter called gnus-distraction-threshold. If a
>> group has fewer than gnus-distraction-threshold unread articles, it won't
>> be displayed.
>
> Interesting. This is something that I could well imagine using in a
> couple of the topics I have.
It's been especially useful for me when work is crazy busy. During those
times the only work-related groups I want to see are the ones with unread
articles. Ticked articles represent things that would be nice to catch up
on one day; unread articles must be handled ASAP.
Since posting the original version I've added a feature or two. I'll clean
it up and repost soon.
> Do you have copyright assignment papers on file with the FSF?
I don't would would be glad to. What do I do?
Katsumi mentioned filing papers when we were discussing some suggestions
and patches I made for nnrss.
I'm almost done adding Etag support to nnrss. It makes nnrss a lot faster.
There's just one *tiny* bug which makes nnrss-group-alist grow without
bound :)
next prev parent reply other threads:[~2006-04-16 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 1:20 Mark Plaksin
2006-04-14 15:17 ` Lars Magne Ingebrigtsen
2006-04-16 20:27 ` Mark Plaksin [this message]
2006-04-17 8:59 ` Lars Magne Ingebrigtsen
2006-04-26 16:32 ` Reiner Steib
2006-04-14 18:13 ` Leon
2006-04-16 20:28 ` Mark Plaksin
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=wsbqv1s1u0.fsf@stone.tss.usg.edu \
--to=happy@mcplaksin.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).