Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: Re: Restricting frequency of 'g'
Date: Sat, 09 Oct 2010 17:50:29 +0200	[thread overview]
Message-ID: <y9bp73tlfe.fsf@news.eternal-september.org> (raw)
In-Reply-To: <m3lj6774zk.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 09 Oct 2010 17:36:31 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> "Jason L Tibbitts III" <tibbs@math.uh.edu> writes:
>
>> Actually I've been looking for something like that for quite some time.
>> For most of my reading, there's really no point in bothering to visit a
>> high-traffic group until it has a quantity of articles in it.
>
> Yes, I can see attraction of something like that.  Russ' implementation
> is based on scanning frequency, while the Mark Plaksin's is based more
> on the number of articles in the group, and Ted's is based on not
> showing the details of how many articles there are unread.
>
> So we seem to have at least three different approaches to the same
> idea.  It could be that this is the sort of thing that's difficult to
> provide, but requires that people just write their own variations to fit
> their own needs.

Hmm. Interesting take. With three different versions already in
existence it would suggest its not that difficult to provide, but more
difficult to choose a "best fit" solution.



      reply	other threads:[~2010-10-09 15:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06  3:36 Russ Allbery
2008-04-06  4:54 ` Bill O'Connor
2008-04-06  6:43   ` Russ Allbery
2008-04-06 11:55 ` John SJ Anderson
2008-04-07  1:30   ` Russ Allbery
2008-04-07 23:45     ` jidanni
2008-04-08  0:54       ` John SJ Anderson
2008-04-08  3:41         ` Russ Allbery
2008-04-08 21:12           ` a Gnus biff (was: Restricting frequency of 'g') Ted Zlatanov
2008-04-09 13:59             ` a Gnus biff Wes Hardaker
2008-04-08  3:55 ` Restricting frequency of 'g' Dan Nicolaescu
2008-04-09  6:49   ` Dan Nicolaescu
2008-04-09 19:22     ` Reiner Steib
2008-04-12 14:58       ` Mark Plaksin
2008-07-29 21:14       ` Dan Nicolaescu
2008-07-30 18:04         ` Reiner Steib
2009-07-30 19:32           ` Dan Nicolaescu
2010-10-07  6:27       ` Dan Nicolaescu
2010-10-07 20:16         ` Lars Magne Ingebrigtsen
2010-10-07 21:55           ` Russ Allbery
2010-10-08 17:28             ` Ted Zlatanov
2010-10-08 15:14           ` Jason L Tibbitts III
2010-10-09 15:36             ` Lars Magne Ingebrigtsen
2010-10-09 15:50               ` Richard Riley [this message]

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=y9bp73tlfe.fsf@news.eternal-september.org \
    --to=rileyrg@googlemail.com \
    --cc=ding@gnus.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).