From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: Arghh, my Gnus is going crazy !!
Date: Wed, 29 Sep 2004 20:46:22 -0500 [thread overview]
Message-ID: <u3c10v89d.fsf@vignette.com> (raw)
In-Reply-To: <plop87lleu52wh.fsf@gnu-rox.org>
Xavier Maillard <zedek@gnu-rox.org> writes:
> On 28 sep 2004, Kevin Greiner wrote:
>
>> test <invalig@toto.com> writes:
>>
>> > Kevin Greiner a écrit :
>> >
>> > > I found, and fixed, the problem. Update from CVS.
>> > > Kevin
>> > >
>> >
>> > What was it ?? :/
>> >
>> > Thank you.
>>
>> gnus-agent-check-overview-buffer. Interestingly, this function
>> was added in 2003-01-14 to help detect obscure errors that were
>> occurring. Now, it's part of the problem.
>
> :/ Thank you for the quick and good support.
>
> Oh BTW, I still have trouble with the synchronization of the
> flags (sutff read/marked during an unplugged session is still
> forgotten when sync is done). I saw it yesterday when I reentered
> my gnus-bug group where I had removed (when unplugged) all the
> spam messages. When back nd after a 'g' on the group, all spam
> messages reappeared :(
Are you up to date? I checked the latest patch about 24 hours ago.
If you're up to date and still having the problem, then I need more
information. What would be best is if you could step through
gnus-agent-synchronize-group-flags. I just added it to try to fix up
the info structures when the flags are sync'd. It works for me. Why
isn't it working for you?
Kevin
next prev parent reply other threads:[~2004-09-30 1:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 12:38 Xavier Maillard
2004-09-25 15:39 ` Kevin Greiner
2004-09-25 22:29 ` Xavier Maillard
2004-09-25 22:54 ` Kevin Greiner
2004-09-26 18:29 ` test
2004-09-27 23:30 ` Kevin Greiner
2004-09-28 6:22 ` Xavier Maillard
2004-09-29 22:13 ` Wes Hardaker
2004-09-30 1:46 ` Kevin Greiner [this message]
2004-09-30 4:39 ` test
2004-09-25 15:47 ` Kevin Greiner
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=u3c10v89d.fsf@vignette.com \
--to=kevin.greiner@vignette.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).