Gnus development mailing list
 help / color / mirror / Atom feed
From: Martin Monsorno <monsorno@gmx.de>
Cc: ding@gnus.org
Subject: Re: error with Group parameter display
Date: Mon, 26 Nov 2001 09:22:24 +0100	[thread overview]
Message-ID: <lr3d32djr3.fsf@loki.exolution.lan> (raw)
In-Reply-To: <vafd729ihmu.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Fri, 23 Nov 2001 17:20:09 +0100")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Martin Monsorno <monsorno@gmx.de> writes:
>
>> Supplement: if the group contains no ticked articles, then
>>
>> - if the group contains new articles, only the new ones are shown.
>>
>> - if the group contains no new articles, all of them are shown.
>>
>> Expired articles are not shown in any of the 2 cases.
>
> This seems to be just like the default behavior, except that the
> default behavior also shows expired messages in the second case.
>

Well, the rule says: "Show me all un-expired articles." Full stop. I
would understand that as "Show me _all_ un-expired articles, in _any_
case, do not distinguish between groups containing new or unticked
articles." Or am I wrong?

> And what do you want?
>
> Maybe you need to list all of the article types you want, rather than
> using negation.
>

Well, I suppose the "error" is, that Gnus shows a different set of
articles if a group contains marked or ticked articles or if it does
not.

Sorry, I hope I have made it clear now. Thanks for your patience.

-- 
Martin Monsorno
mailto:monsorno@gmx.de



  reply	other threads:[~2001-11-26  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 17:36 Martin Monsorno
2001-11-22 17:59 ` Kai Großjohann
2001-11-23  9:15   ` Martin Monsorno
2001-11-23 10:36     ` Kai Großjohann
2001-11-23 15:32     ` Martin Monsorno
2001-11-23 16:20       ` Kai Großjohann
2001-11-26  8:22         ` Martin Monsorno [this message]
2001-11-26  8:58           ` Kai Großjohann
2001-12-29  3:13             ` Lars Magne Ingebrigtsen

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=lr3d32djr3.fsf@loki.exolution.lan \
    --to=monsorno@gmx.de \
    --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).