Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: hput via "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" <info-gnus-english@gnu.org>
To: info-gnus-english@gnu.org
Subject: Something peculiar in my Topics setup
Date: Thu, 09 Jun 2022 21:57:55 +0000	[thread overview]
Message-ID: <87o7z1biu4.fsf@local.lan> (raw)


First, I've been using topics in gnus for many years and have not seen
this before.

I have a topic: Watch

Under that topic a number of nnml:directories of certain groups.

One is nnml:all-but-cron_

That group gets copies of all but a select few groups incoming mail.

Sort of a fallback if I lose track of mail in one of the many many
nnml groups.

OK, it nearly always has unread messages.

So one would expect what ever number that is would show up in the
total shown at topic 'watch'. But what I see at topic watch is:

    [ watch -- 0 ]...

No new messages whatsoever.  Not only that but if I do C-u <ret>
telling topic watch to spill its groups, it pops out with:

    [ watch -- 0 ]
      [ banks -- 0 ]
             0: nnml:Chase
             0: nnml:CarringtonBank
             0: nnml:BankOfAmerica
             0: nnml:DSCC
             0: nnml:DSCB
*            0: nnml:synchronyBankAlerts
*            0: nnml:Golden1

But if I press 'j' and give the groupname: nnml:all-but-cron_

Look what happens:

    [ watch -- 0 ]
         235: nnml:all-but-cron_
      [ banks -- 0 ]
             0: nnml:Chase
             0: nnml:CarringtonBank
             0: nnml:BankOfAmerica
             0: nnml:DSCC
             0: nnml:DSCB
*            0: nnml:synchronyBankAlerts
*            0: nnml:Golden1

It was there under watch all along... and with unread messages which
should have shown at `watch'

and C-u <RET> on watch should have dumped it into sight.

So the topic watch neither registers the unread messaages in
nnml:all-but-cron_

Nor displays nnml:all-but-cron_ when asked with C-u <RET> on `watch'.

futher there are others with unread messages under there too:

`J' nnml:inco <ret>  and see what we get:

    [ watch -- 0 ]
         256: nnml:inco
         235: nnml:all-but-cron_
      [ banks -- 0 ]
             0: nnml:Chase
             0: nnml:CarringtonBank
             0: nnml:BankOfAmerica
             0: nnml:DSCC
             0: nnml:DSCB
*            0: nnml:synchronyBankAlerts
*            0: nnml:Golden1

nnml:inco comes out from under `watch' also with unread messages.

This is all wrong wrong wrong... and I've never noticed something like
it to happen.

Can anyone offer a guess as to what is causing "topic modes'" misbehavior?



             reply	other threads:[~2022-06-09 21:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 21:57 hput via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English) [this message]
2022-06-09 22:08 ` Emanuel Berg
2022-06-11  0:21   ` hput via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)
2022-06-10 11:31 ` Adam Sjøgren
2022-06-11  0:32   ` hput via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)
2022-06-11  0:43     ` hput via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)
2022-06-11  1:25       ` hput via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)
2022-06-11  8:54     ` Adam Sjøgren

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=87o7z1biu4.fsf@local.lan \
    --to=info-gnus-english@gnu.org \
    --cc=hputn3@zohomail.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).