Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Re: cannot catchup
Date: Fri, 04 Mar 2005 09:50:29 -0500	[thread overview]
Message-ID: <usm3blb2i.fsf@boost-consulting.com> (raw)
In-Reply-To: <iluhdjtn4vr.fsf@latte.josefsson.org>

Simon Josefsson <jas@extundo.com> writes:

> Sam Steingold <sds@gnu.org> writes:
>
>>> * Sam Steingold <fqf@tah.bet> [2005-03-01 17:24:58 -0500]:
>>>
>>> I hit "c" or "C" on a newsgroup to mark everything as read,
>>> and it now says that there are no new articles.
>>> when I hit "g", however, all the 12,000 new articles are new again.
>>> I cannot spend 10hours waiting for gnus to enter the group with 12,000
>>> new articles, so how do I read it?
>>
>> it appears that I have two identical groups:
>>
>>    s6U 2989n  0s 12328o  gmane.comp.gnu.mingw.user             20040622T122410 
>>    s6U 2989n  0s 12328o  gmane.comp.gnu.mingw.user             20040622T122410 
>>
>> "^" in *Groups*, then RET on gmane in *Servers*, then "u" on an
>> unsubscried group ==> 2 such groups.
>
> If you kill both groups, restart emacs, and subscribe to the group
> again, can you reproduce this?  I suspect the server name for one of
> the identical groups is slightly off, so equality comparison fails.
> `G E' on the groups will tell.
>
> (The reason killing both groups and subscribing to it again, without
> restarting emacs, might not be enough is that groups linger around in
> some structures when they are killed.)

I've experinced the same thing, over and over again, intermittently.
Normally I end up entering the group and doing `c' there, and also
doing it from the *Groups* buffer.  Eventually it responds :(


-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com




      reply	other threads:[~2005-03-04 14:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 22:24 Sam Steingold
2005-03-01 22:56 ` Vasily Korytov
2005-03-02 20:00 ` Sam Steingold
2005-03-02 20:56   ` Simon Josefsson
2005-03-04 14:50     ` David Abrahams [this message]

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=usm3blb2i.fsf@boost-consulting.com \
    --to=dave@boost-consulting.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).