Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Plaksin <happy@mcplaksin.org>
Subject: Recent gnus-get-unread-articles changes cause trouble
Date: Thu, 03 Jun 2004 21:40:53 -0400	[thread overview]
Message-ID: <m3u0xsnlqy.fsf@water.tss.usg.edu> (raw)

Hi,

After the first change (rev 7.16) below, I started seeing weirdness with g in
the Group buffer.  I have several nnvirtual groups at level 4.  They happen
to contain only nnrss groups.  If I do 4 g I see the nnrss groups being
checked but when gnus-group-get-new-news finishes, these groups show up with
an asterisk in place of the number of unread articles.  If I ESC g while
pointing at the nnvirtual group, everything works as expected.

Reverting to rev 7.15 of gnus-start.el resolves the problem.

Possibly related is the discussion in this long thread:
http://thread.gmane.org/gmane.emacs.gnus.general/56066

Before I try to debug it I thought I'd see if anybody else had ideas off the
top of their heads :)

Thanks for any help!

revision 7.18
date: 2004/05/21 10:41:21;  author: yamaoka;  state: Exp;  lines: +16 -13
(gnus-get-unread-articles): Cosmetic change.
----------------------------
revision
7.17
date: 2004/05/21 04:03:38;  author: yamaoka;  state: Exp;  lines: +5 -3
(gnus-get-unread-articles): Fix previous commit.
----------------------------
revision 7.16
date: 2004/05/21 00:34:56;  author: yamaoka;  state: Exp;  lines: +1 -1
(gnus-get-unread-articles): Don't invalidate active for foreign groups
even if the group level is higher than the specified value.
 




             reply	other threads:[~2004-06-04  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04  1:40 Mark Plaksin [this message]
2004-06-04  1:45 ` Mark Plaksin
2004-06-04  2:38 ` Katsumi Yamaoka

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=m3u0xsnlqy.fsf@water.tss.usg.edu \
    --to=happy@mcplaksin.org \
    /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).