Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: virtual nnvirtual
Date: Wed, 23 Mar 2022 15:31:30 +0000	[thread overview]
Message-ID: <87o81wr8h9.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87sfr8iuib.fsf@ericabrahamsen.net>

On Wednesday, 23 Mar 2022 at 08:00, Eric Abrahamsen wrote:
> As Andy mentioned, this is also kind of a philosophical/design question.

Indeed.

> Personally I would find it less surprising if you didn't get
> any messages from long-inactive groups until you "dug all the way back"

As would I.

> in time to them, but that would require a different code approach (and
> probably would be less efficient).

I guess the alternative would retrieve articles from each group, sort
them, and then prune the list to the desired size.  But not really
necessary, once the algorithm is understood!  I can live with the
current approach, knowing how to get what I want.

thank you,
eric
-- 
Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.2



  reply	other threads:[~2022-03-23 15:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23  0:45 Andrew Cohen
2022-03-23  8:14 ` Eric S Fraga
2022-03-23 11:53 ` Eric S Fraga
2022-03-23 12:02 ` Eric S Fraga
2022-03-23 12:53   ` Andrew Cohen
2022-03-23 13:19     ` Eric S Fraga
2022-03-23 14:51       ` Andrew Cohen
2022-03-23 15:28         ` Eric S Fraga
2022-03-23 15:00       ` Eric Abrahamsen
2022-03-23 15:31         ` Eric S Fraga [this message]
2022-03-24  5:30       ` Andrew Cohen
2022-03-24  7:27         ` Eric S Fraga
2022-03-23 15:33 ` Eric S Fraga
2022-03-25  0:39   ` Andrew Cohen
2022-03-25  4:53     ` Andrew Cohen
2022-03-25  9:15       ` Eric S Fraga
2022-03-25  9:27         ` Andrew Cohen
2022-03-25  9:35           ` Eric S Fraga
2022-03-25  9:39             ` Andrew Cohen

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=87o81wr8h9.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).