From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Problem entering Foreign Groups
Date: 01 Jul 1998 12:59:38 +0200 [thread overview]
Message-ID: <m3g1glalb9.fsf@sparky.gnus.org> (raw)
In-Reply-To: Eze Ogwuma's message of "01 Jul 1998 03:21:34 +0100"
Eze Ogwuma <zcaceog@localhost.localdomain> writes:
> ((1 . 7094) (7096 . 70 99)) ((cache 6110 6113 (7083 . 7084) 7088)
> (tick (7083 . 7084) 7088))
Well, this looks totally whacked out.
((1 . 7094) (7096 . 70 99))
That should be impossible. Has a space snuck in between "70" and
"99"?
> Because of this these commands were called after the "group" command.
>
> >From *nntp-log*
>
> 19980701T001727 news.dircon.co.uk XOVER 7095-7095
> 19980701T001727 news.dircon.co.uk XOVERVIEW 7095-7095
> 19980701T001727 news.dircon.co.uk HEAD 7095
[...]
> 423 no such article number in this group
> 423 no such article number in this group
[...]
> The headers for 7147-7192 are then downloaded.
>
> Then the program freezes.
It would seem that it reacts inappropriately to getting a lot of 423
lines. Hm. Yup: `nntp-next-result-arrived-p' looks highly bogus. If
we have gotten half an error line, Gnus would loop forever with point
in the middle of that line.
Could you check after 5.6.23 has been released whether it fixes this bug?
> Why was "XOVERVIEW 7095-7095" called? was it because the result of "XOVER
> 7095-7095" was "."?
Yes.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-07-01 10:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-10 16:25 Eze Ogwuma
1998-06-20 4:47 ` Eze Ogwuma
1998-06-24 4:35 ` Lars Magne Ingebrigtsen
1998-06-24 6:27 ` Eze Ogwuma
1998-06-24 8:26 ` Eze Ogwuma
1998-06-24 22:41 ` Lars Magne Ingebrigtsen
1998-06-26 15:12 ` Eze Ogwuma
1998-06-24 22:40 ` Lars Magne Ingebrigtsen
1998-06-28 23:47 ` Eze Ogwuma
1998-06-29 20:28 ` Lars Magne Ingebrigtsen
1998-07-01 2:21 ` Eze Ogwuma
1998-07-01 10:59 ` Lars Magne Ingebrigtsen [this message]
1998-07-01 11:17 ` Eze Ogwuma
1998-07-01 11:25 ` Lars Magne Ingebrigtsen
1998-07-01 15:26 ` Eze Ogwuma
1998-07-15 7:58 ` Lars Magne Ingebrigtsen
1998-07-15 8:52 ` Eze Ogwuma
1998-07-15 9:11 ` Eze Ogwuma
1998-07-15 14:09 ` Lars Magne Ingebrigtsen
1998-07-16 1:53 ` Eze Ogwuma
1998-07-18 20:19 ` Lars Magne Ingebrigtsen
1998-07-19 13:18 ` Eze Ogwuma
1998-07-25 10:26 ` Eze Ogwuma
1998-07-26 15:37 ` Lars Magne Ingebrigtsen
1998-07-28 4:11 ` Eze Ogwuma
1998-07-30 21:14 ` Lars Magne Ingebrigtsen
1998-07-30 22:59 ` Eze Ogwuma
1998-07-30 23:19 ` Lars Magne Ingebrigtsen
1998-07-30 23:45 ` Eze Ogwuma
1998-07-31 10:24 ` Kai Grossjohann
1998-07-31 12:43 ` Eze Ogwuma
1998-07-31 14:13 ` Kai Grossjohann
1998-08-01 19:07 ` Harry Putnam
1998-08-01 20:08 ` Eze Ogwuma
1998-07-31 14:43 ` Lars Magne Ingebrigtsen
1998-07-31 17:47 ` Kai Grossjohann
1998-08-01 14:32 ` Lars Magne Ingebrigtsen
1998-07-01 11:06 ` Eze Ogwuma
1998-06-27 2:37 ` Eze Ogwuma
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=m3g1glalb9.fsf@sparky.gnus.org \
--to=larsi@gnus.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).