Gnus development mailing list
 help / color / mirror / Atom feed
From: kgreiner@xpediantsolutions.com
Subject: Re: gnus-agent-fetch-selected-article
Date: Tue, 07 Jan 2003 23:22:13 -0600	[thread overview]
Message-ID: <uptr88bcq.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <u8z8yy3r3ck.fsf@blackbird-2k.MITRE.ORG>

David S Goldberg <david.goldberg6@verizon.net> writes:

>>>>>> On Wed, 01 Jan 2003 18:12:16 +0100, kai.grossjohann@uni-duisburg.de (Kai Großjohann) said:
>
>> David S Goldberg <david.goldberg6@verizon.net> writes:
>>> So there's apparently something unique about those groups that's
>>> biting me, but for the life of me, I can't quite figure it out.
>
>> Number of dormant or ticked messages?  I think I'm seeing the problem
>> in groups with no dormant or ticked messages.
>
> Actually both have at least a few ticked messages.  Neither has any
> dormant, but then neither do most of my other groups.
>
>> Oh, err.  I think I might be seeing a different problem: all unread
>> articles disappear when I enter a group.  Hitting C-x u in the group
>> buffer, then J u on the group, fixes the problem.
>
> This sounds similar to what I'm seeing (new messages don't show up,
> only the ticks) but I haven't had any luck with J u, only
> gnus-agent-regenerate(-group) seems to fix it for me.  I also avoid
> need C-x u in the group buffer by exiting the group with Q.

To be absolutely honest, I can't think of any way for the agent to
mess up this selectively.

David, please make a backup of your group's .overview and .agentview
files before executing gnus-agent-regenerate-group.  You should then
be able to compare the old/new versions to see what regenerate
changed.  If you can tell me what regenerate is fixing, it may help me
understand what is breaking.

Kevin



  reply	other threads:[~2003-01-08  5:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021211092015.18546.h016.c001.wm@mail.xpediantsolutions.com.criticalpath.net>
2002-12-13 17:31 ` gnus-agent-fetch-selected-article David S Goldberg
2002-12-13 19:00   ` gnus-agent-fetch-selected-article David S Goldberg
2002-12-13 19:27     ` gnus-agent-fetch-selected-article David S Goldberg
2002-12-14  5:34       ` gnus-agent-fetch-selected-article kgreiner
2002-12-31 15:01         ` gnus-agent-fetch-selected-article David S Goldberg
2003-01-01 17:12           ` gnus-agent-fetch-selected-article Kai Großjohann
2003-01-02 15:14             ` gnus-agent-fetch-selected-article David S Goldberg
2003-01-08  5:22               ` kgreiner [this message]
2003-01-08 16:34                 ` gnus-agent-fetch-selected-article David S Goldberg
2003-01-09 22:48                   ` gnus-agent-fetch-selected-article kgreiner
2003-01-15 20:36                     ` gnus-agent-fetch-selected-article David S Goldberg
2003-01-17  4:07                       ` gnus-agent-fetch-selected-article Kevin Greiner
2003-01-22 21:05                         ` gnus-agent-fetch-selected-article David S Goldberg
2003-02-12 18:36                         ` gnus-agent-fetch-selected-article David S Goldberg
2002-12-13 19:30   ` gnus-agent-fetch-selected-article kgreiner
2002-12-13 19:42     ` gnus-agent-fetch-selected-article David S Goldberg
2002-12-14 12:55   ` gnus-agent-fetch-selected-article Kai Großjohann
2002-12-11 16:52 gnus-agent-fetch-selected-article David S Goldberg
2002-12-13 11:17 ` gnus-agent-fetch-selected-article Kai Großjohann

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=uptr88bcq.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).