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: Re: Something peculiar in my Topics setup
Date: Sat, 11 Jun 2022 00:21:19 +0000	[thread overview]
Message-ID: <87r13wm4n4.fsf@local.lan> (raw)
In-Reply-To: <87czfhxzfn.fsf@dataswamp.org>

Emanuel Berg <incal@dataswamp.org> writes:

> hput wrote:
>
>> [ watch -- 0 ]
>>      235: nnml:all-but-cron_
>
> Did you cronfigure `gnus-topic-line-format'?

No I never have.  However the groups under watch have always displayed
as expected, that is if they had unread messages that number would be
reflected tin watch topic.

Currently is says zero although there over 200 unread in two groups.
I've used tops for years and had the watch topic for equally long.
Not counting various miss-haps down thru the years.



  reply	other threads:[~2022-06-11  0:21 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)
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) [this message]
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=87r13wm4n4.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).