From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Question about article identification and backends.
Date: Tue, 20 May 2003 12:33:45 -0500 [thread overview]
Message-ID: <87u1bpseti.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <84n0hir79r.fsf@lucy.is.informatik.uni-duisburg.de> ( =?iso-8859-1?q?Kai_Gro=DFjohann's_message_of?= "Mon, 19 May 2003 22:49:52 +0200")
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> Why 101? We were talking about all articles having a unique id in
> the whole backend. This means that there was no article 42
> previously in the group -- there is only one article with number 42.
>
> (Articles coming from other backends should get new, higher, numbers,
> I guess.)
So with respect to ordering the articles in a group, were you thinking
that gnus would:
- just keep a separate per-group list ordering the articles in a
group.
- default to order by "Date:" (or some new "X-Gnus-Arrival-Date:" header).
- default to order by the unique article ID, presuming that the ID
included the arrival date (a la maildir?).
- something else.
In particular, if when I enter a large group and gnus asks me how many
articles, how would that article subset be chosen? I'd really like
for it to always be the N most recent articles either by Date: or
arrival date by default.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
next prev parent reply other threads:[~2003-05-20 17:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-17 19:56 Rob Browning
2003-05-17 21:29 ` Andreas Fuchs
2003-05-18 2:57 ` Rob Browning
2003-05-18 3:19 ` Rob Browning
2003-05-18 9:52 ` Kai Großjohann
2003-05-18 18:38 ` Rob Browning
2003-05-18 18:50 ` Rob Browning
2003-05-19 13:02 ` Kai Großjohann
2003-05-19 13:02 ` Kai Großjohann
2003-05-19 16:57 ` Paul Jarc
2003-05-19 16:47 ` Paul Jarc
2003-05-19 20:49 ` Kai Großjohann
2003-05-19 20:57 ` Paul Jarc
2003-05-20 10:56 ` Kai Großjohann
2003-05-20 17:33 ` Rob Browning [this message]
2003-05-22 7:04 ` Kai Großjohann
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=87u1bpseti.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).