Gnus development mailing list
 help / color / mirror / Atom feed
From: Pavel.Janik@linux.cz (Pavel Janík ml.)
Subject: Re: Additional to level topic?
Date: Mon, 5 Jun 2000 17:00:23 +0200	[thread overview]
Message-ID: <m31z2c6umq.fsf@totally-fudged-out-message-id> (raw)
In-Reply-To: Shenghuo ZHU's message of "05 Jun 2000 10:30:18 -0400"

   From: Shenghuo ZHU <zsh@cs.rochester.edu>
   Date: 05 Jun 2000 10:30:18 -0400

Hi,

   > > Topic as "Virtual". You will have one virtual Top Level Topic which will
   > > not be shown as top level. His sons (the second level topics) will then be
   > > shown as top level. I think this is the solution for this, isn't it?
   > 
   > Is it much different from showing topic "Gnus"?

yes, because you can have a number of unread (or whatever) articles in the
Topic line and this way, you can not have two (or more) completely
separated hierarchies. A real-world example can be this: imagine you are
storing all outgoing mail to the nnfolder files one per month, you would
like to see them all the time, articles there are unread and are counted as
such in the Topic in which you have them, this count is also in the top
level Topic. So you can have everything read and you still have these big
numbers in the top level Topic all the time. Or is it solvable for normal
users? I can create user-function and count only articles in the
non-archiving groups, but I'm trying to force Gnus usage for non-lispers
here.
-- 
Pavel Janík ml.
Pavel.Janik@linux.cz



  reply	other threads:[~2000-06-05 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-04 20:59 Pavel Janík ml.
2000-06-04 22:01 ` Shenghuo ZHU
2000-06-05  5:28   ` Pavel Janík ml.
2000-06-05 14:30     ` Shenghuo ZHU
2000-06-05 15:00       ` Pavel Janík ml. [this message]
2000-06-05 22:25         ` Kai Großjohann
2000-06-06 16:12           ` Pavel Janík ml.
2000-06-06 17:35             ` Shenghuo ZHU
2000-06-07 12:26               ` Pavel Janík ml.
2000-06-09 18:11                 ` David S. Goldberg
2000-08-13 18:21               ` 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=m31z2c6umq.fsf@totally-fudged-out-message-id \
    --to=pavel.janik@linux.cz \
    /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).