Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Marcus Frings <iam-est-hora-surgere@despammed.com>
Subject: Re: gnus not showing all articles in a group
Date: Fri, 08 Aug 2003 14:16:44 +0200	[thread overview]
Message-ID: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-878yq4ny37.fsf@gothgoose.net> (raw)
In-Reply-To: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87d6fgo0t8.fsf@gothgoose.net>

* Marcus Frings <iam-est-hora-surgere@despammed.com> wrote:
> * Kathryn Huxtable <kathryn@kathrynhuxtable.org> wrote:

>>    No, that's a matter of design of Gnus, fixing this would  mean
>> reimplementation of major parts of Gnus'  back ends. Gnus thinks
>> "highest-article-number -  lowest-article-number =
>> total-number-of-articles". This  works OK for Usenet groups, but if you
>> delete and move  many messages in mail groups, this fails. To cure the
>> symptom, enter the group via `C-u RET'  (this makes Gnus get all
>> messages), then  hit `M P b' to mark all messages and  then say `B m
>> name.of.group' to move  all messages to the group they have been in
>> before, they  get new message numbers in this process and the count is
>> right again (until you delete and move your mail to other  groups
>> again).

> If I do this as you suggest my article sorting in these groups don't
> work anymore. I use `gnus-thread-sort-by-most-recent-number' in my
> gnus_groupparameters.el and afterwards the oldest mails are at the top
> and the newest at the bottom. Obviously the article numbers seem to
> change. So I tried `gnus-thread-sort-by-most-recent-date' (which is said
> to be slower than -number) instead but this has an effect on only one
> certain group somehow whereas other groups don't seem to be affected.

Ups, I forgot to mention that I also played with
gnus-article-sort-functions (changing `gnus-article-sort-by-number' to
`gnus-article-sort-by-date') but the older articles are still at the
top.

Regards,
Marcus
-- 
"Paranoia - das heißt doch nur, die Wirklichkeit
realistischer zu sehen als andere."


  reply	other threads:[~2003-08-08 12:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <i71xvxoncv.fsf@crpppc215.epfl.ch>
     [not found] ` <yoijhe4t7ltr.fsf@frealaf.dd.chalmers.se>
     [not found]   ` <2qptjhmzhl.fsf@crpppc215.epfl.ch>
2003-08-07 12:30     ` Kathryn Huxtable
     [not found]       ` <85he4t8pxb.fsf.hcanon@alussinan.org>
2003-08-07 15:33         ` Reiner Steib
2003-08-08 11:17       ` Marcus Frings
2003-08-08 12:16         ` Marcus Frings [this message]
     [not found]         ` <85wudoxocc.fsf.hcanon@alussinan.org>
2003-08-08 19:19           ` Marcus Frings
     [not found]             ` <v9vft83p2y.fsf@marauder.physik.uni-ulm.de>
     [not found]               ` <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87oeyzls35.fsf@gothgoose.net>
2003-08-09 13:14                 ` Reiner Steib
2003-08-09 16:28                   ` Marcus Frings
2003-08-07 13:01     ` Frank Schmitt
     [not found] ` <2wwudpn06p.fsf@crpppc215.epfl.ch>
2003-08-07 13:19   ` Johan Bockgård

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=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-878yq4ny37.fsf@gothgoose.net \
    --to=iam-est-hora-surgere@despammed.com \
    --cc=protagonist@gmx.net \
    /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).