Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Drafts and archive groups under topics (was: Problem with gnus-topic-display-empty-topics?)
Date: Fri, 12 Dec 2003 12:41:59 -0500	[thread overview]
Message-ID: <m3d6au0w7s.fsf@asfast.com> (raw)
In-Reply-To: <m3smjsiqai.fsf@asfast.com>

> Even though `gnus-topic-display-empty-topics' is set to `t' for me, if I
> select a topic with `RET' or `SPACE', I don't see any of the groups
> within that topic, except those groups containing unread or marked
> articles.
>
> I have to invoke `C-u RET' or `C-u SPACE' on the topic line in order to
> see all the groups within it ... even those groups which are configured
> to be "Permanently Visible" in their own group parameters.

I have figured out more about when behavior occurs:

I have moved my drafts ("nndraft:") and archive ("nnml+archive:") groups
each into their own topics.  In these topics, and in _only_ these
topics, I have to invoke `C-u RET' or `C-u SPACE' to view the groups.
If I invoke `RET' or `SPACE' for these topics, they don't "open" to show
me the groups.

What could be special about `nndraft:' and `nnml+archive:' groups which
would cause this?  Is there a way to cause these types of groups to be
handled the same as all the others, when they are inside of a topic?

Thanks in advance.

-- 
 Lloyd Zusman
 ljz@asfast.com




  parent reply	other threads:[~2003-12-12 17:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10 16:35 Problem with gnus-topic-display-empty-topics? Lloyd Zusman
2003-12-11 13:47 ` Robert Epprecht
2003-12-11 13:59   ` Lloyd Zusman
2003-12-12 17:41 ` Lloyd Zusman [this message]
2003-12-12 18:22   ` Drafts and archive groups under topics Lloyd Zusman
2003-12-15 11:55     ` Kai Grossjohann

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=m3d6au0w7s.fsf@asfast.com \
    --to=ljz@asfast.com \
    /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).