From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Subject: Re: Summarize from a partial NNTP read
Date: Thu, 25 Jun 1998 21:03:11 +0200 [thread overview]
Message-ID: <HBF.980625onv5@bombur2.uio.no> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Wed, 24 Jun 1998 04:52:55 GMT"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>Hallvard B Furuseth <h.b.furuseth@usit.uio.no> writes:
>> Sometimes the server hangs when it has sent 40-200 K headers. (Well,
>> Gnus hangs anyway, I don't know what the server is doing.)
>
> Hm. Well, it would be interesting to find out why that happens...
Tell me what to debug and I'll try some day.
>> In both cases, I'd like to ^G and generate a *Summary* of the headers
>> that the server did manage to send. Is that possible?
>
> It actually wouldn't be that difficult to do -- one could just catch
> the `C-g' (when fetching headers) and then just point Gnus at the
> half-arrived headers. Gnus assumes that any articles it can't get
> headers for have expired, so one would have to do something about
> that, which means that I think it's too much work anyway.
Maybe it would be simpler to not catch the C-g, and not clean up after
the partial fetch (until the next Gnus command, anyway). Then the user
could call a command similar to `gnus-group-select-group' which would
use the previous NNTP data instead of rereading NNTP, and pretend it
only asked for the headers that were actually received.
--
Hallvard
next prev parent reply other threads:[~1998-06-25 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-21 17:21 Hallvard B Furuseth
1998-06-24 4:43 ` Lars Magne Ingebrigtsen
1998-06-25 19:03 ` Hallvard B Furuseth [this message]
1998-06-27 1:24 ` Lars Magne Ingebrigtsen
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=HBF.980625onv5@bombur2.uio.no \
--to=h.b.furuseth@usit.uio.no \
/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).