From: Michael J. Barillier <mbarilli@midsouth.rr.com>
Subject: Unread/total article count on startup */0?
Date: Fri, 20 May 2005 15:47:21 GMT [thread overview]
Message-ID: <8764xd99xb.fsf@shadizar.dyndns.org> (raw)
After rewriting my .emacs.el and .gnus files and purging my moderately
hosed Gnus setup, I now see that the Gnus group buffer shows ``*/0''
for the unread/available article counts (I've got "%y/%t" in
`gnus-group-line-format') when Gnus starts. If I select a group and
then return to the group buffer the counts change to the correct
values. What's up with that? Did I forget to set some variable
correctly to have Gnus query the server for the number of
unread/available articles, or is this WAD? (Prior to scrubbing my
setup, the counts were OK on startup as I'd have expected.)
--
Michael J. Barillier | ``When you have to shoot,
blackwolf(at)shadizar.dyndns.org | shoot. Don't talk.''
http://shadizar.dyndns.org/~blackwolf/ | -- Tuco Ramirez
Public key 0x35E54973: EDB9 4FBC 4D0B 070C C0E3 2EE4 D822 78CE 35E5 4973
reply other threads:[~2005-05-20 15:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8764xd99xb.fsf@shadizar.dyndns.org \
--to=mbarilli@midsouth.rr.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).