Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: small agent irritation
Date: 16 Sep 2000 13:22:06 -0700	[thread overview]
Message-ID: <m2lmwsxf2p.fsf@gnus-5.8.8-cvs.now.playing> (raw)


This is a small gripe that comes up from time to time on my setup.
Not sure of the exact circumstances that bring this on but
occasionally I'll notice a post I want to be downloaded under agent
that has already be read for one reason or anther in `Plugged' mode.

Usually just marking it unread again with `M-u' leaving the group
going plugged and running J u on that group will do it, but
occasionally this does not work.  In the present cast the missing
message is actually in the agentized group as evidenced by
ls ~News/agent....../group/<number>

No amout of redownloading will help this... so I tried to edit
.agentview and .overview for that group.

Adding the file number to .agentview in the same way  others appear:
(16765 . t)

Adding to .overview by inserting the tabs and information as other
files have.  What looks like the normal Nov data.

file#   subject  from  date  message-id  references  charcters  lines

Only with tabs instead of spaces.
Still doesn't show up.  Even `j' with that file number won't find it.
But ls shows it to be on disk, in that group directory.



             reply	other threads:[~2000-09-16 20:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-16 20:22 Harry Putnam [this message]
2000-09-16 21:14 ` ShengHuo ZHU
2000-09-16 21:35   ` Harry Putnam
2000-09-16 22:00     ` ShengHuo ZHU
2000-09-16 22:29       ` Harry Putnam
2000-09-16 23:10         ` ShengHuo ZHU
2000-09-17  4:13           ` Harry Putnam
2000-09-17 10:05 ` Christoph Rohland
2000-09-17 13:23   ` Harry Putnam

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=m2lmwsxf2p.fsf@gnus-5.8.8-cvs.now.playing \
    --to=reader@newsguy.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).