Gnus development mailing list
 help / color / mirror / Atom feed
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: ding@gnus.org
Subject: Recovering from broken connection
Date: Mon, 29 Oct 2007 15:12:21 +0200	[thread overview]
Message-ID: <20071029131220.GA2475@kobe.laptop> (raw)

While I was fetching articles with the agent, my dialup connection died,
and left many articles in a `strange' state.  They are listed as:

    00-00-00 [   0: Gnus Agent          ] [Undownloaded article 58998]

in the summary buffer, but hitting SPC or RET on them properly displays
both the headers and the article are available, even in offline mode.

I tried setting `gnus-agent-consider-all-articles' and refetching, but
this doesn't seem to have regenerated the summary buffers which are
`broken'.  Is there any way to force Gnus to query the agent again,
since these articles *are* available when I am offline?

For example, here's how my current summary buffer for news:comp.std.c
looks:

 . 00-00-00 [   0: Gnus Agent          ] [Undownloaded article 58998]
 . 00-00-00 [   0: Gnus Agent          ] [Undownloaded article 58999]
 . 00-00-00 [   0: Gnus Agent          ] [Undownloaded article 59000]
 . 2007-10-28 [  46: cr88192             ] Re: Floating point question
 .+2007-10-29 [  54: Keith Thompson      ] Does a constraint violation cause undefined behavior?
 . 2007-10-29     [  68: James Kuyper        ] Re: Does a constraint violation cause undefined behavior?
 . 2007-10-29     [  11: Wojtek Lerch        ] Re: Does a constraint violation cause undefined behavior?

In larger groups, i.e. in news:comp.lang.c the undownloaded articles are
many dozens, and it is a pain reading them without any sort of threading
or sorting :/

- Giorgos



                 reply	other threads:[~2007-10-29 13:12 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=20071029131220.GA2475@kobe.laptop \
    --to=keramida@ceid.upatras.gr \
    --cc=ding@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).