From: Leon <sdl.web@gmail.com>
Subject: Re: CODE: Hide groups with few unread articles
Date: Fri, 14 Apr 2006 19:13:42 +0100 [thread overview]
Message-ID: <m2lku89ga1.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <m3vf6qxig2.fsf@water.tss.usg.edu>
Mark Plaksin <happy@usg.edu> writes:
> Here's some code that lets you hide groups when they have just a few unread
> articles. You can set the threshold on a per-topic and/or per-group basis.
>
> I use levels to separate my groups by priority but I am subscribed to a lot
> of groups so each level contains a lot of groups. I'm easily distracted so
> I wanted a way to hide groups without many unread articles. That way when
> I check for new messages I don't end up reading two or three articles in
> each of 25 groups. Instead I generally end up reading one or two groups
> with 25 articles each.
>
> It requires a small patch to gnus-group.el which allows you to specify the
> predicate to use in the funcall to gnus-group-prepare-function. That's the
> first attachment. The second attachment does the rest of the work.
>
> 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. gnus-distraction-threshold defaults to 1 so nothing should
> change unless you set the threshold somewhere. As with any group parameter
> you can set it for a topic and have it apply to all groups in the topic.
> By default groups with ticked articles are always displayed.
>
> Two key bindings are turned on in the Group buffer:
> - C-cd toggles distraction prevention on and off
> - C-ct toggles the display of groups with ticked articles
>
> I've only been playing with this for a few days so comments and suggestions
> are very welcome!
>
A feature that I have been looking for! Wonderful.
Does it work for topic i.e hide a topic when the total number of
unread articles within a topic is below threshold?
Regards,
--
Leon
next prev parent reply other threads:[~2006-04-14 18:13 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
2006-04-17 8:59 ` Lars Magne Ingebrigtsen
2006-04-26 16:32 ` Reiner Steib
2006-04-14 18:13 ` Leon [this message]
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=m2lku89ga1.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@gmail.com \
/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).