Gnus development mailing list
 help / color / mirror / Atom feed
From: Emerick Rogul <emerick@cs.bu.edu>
Subject: Topic bug?
Date: Fri, 27 Sep 2002 11:07:06 -0400	[thread overview]
Message-ID: <vuo1y7ffp45.fsf@csa.bu.edu> (raw)

Hi,

I'm using the latest development version of Oort Gnus from CVS and
I've noticed what I consider to be a bug with topics.

I have gnus-topic-display-empty-topics set to nil in my .gnus.el, so
empty topics aren't shown by default.  If I want to enter an empty
group for some reason, I hit 'j' and enter the group name.  The group
and the appropriate topic now appear in the group buffer, but only the
topic _directly_ above the group shows up.  I would expect all of the
topics to appear when I jump to the group.  For example, if I have a
layout like this:

  [ topic1 ]
    [ topic2 ]
      [ topic3 ]
        nnml:foo
    [ other topic ]
    [ another topic ]

When I hit 'j', to make nnml:foo appear, I would expect to see all of
the topics containing it displayed as above.  However, this is what I
see instead:

  [ topic1 ]
      [ topic3 ]
        nnml:foo
    [ other topic ]
    [ another topic ]

As you can see, this is a bit confusing, because you don't see topic2
any more (even though indentation indicates that a topic _should_ be
there).  I think it'd be much better if 'j' made nnml:foo, topic1,
_and_, topic2 (and any topics that are parents of topic2) appear in
the group buffer.

Does anyone agree/disagree with this?

-Emerick
-- 
-------------------------------------------------------------------------
Emerick Rogul             /\/     "how young are you, how old am i?
emerick@cs.bu.edu         /\/      let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats



             reply	other threads:[~2002-09-27 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 15:07 Emerick Rogul [this message]
2002-12-29 16:22 ` 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=vuo1y7ffp45.fsf@csa.bu.edu \
    --to=emerick@cs.bu.edu \
    /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).