From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nntp marks getting reset all the time
Date: Wed, 23 Feb 2011 08:32:08 -0600 [thread overview]
Message-ID: <8762saq0t3.fsf@lifelogs.com> (raw)
In-Reply-To: <87sjvezwx4.fsf@dod.no>
On Wed, 23 Feb 2011 14:45:59 +0100 Steinar Bang <sb@dod.no> wrote:
>>>>>> Ted Zlatanov <tzz@lifelogs.com>:
>> On nntp my marks are getting reset semi-randomly to older values. Old
>> `d' read messages show up in the summary buffer again. It's very
>> annoying. I've been coping by saving the marks with gnus-sync, but
>> don't know what I should be bisecting or debugging because it only
>> happens occasionally.
SB> The times I've seen this have been early in the phase of starting to
SB> use gnus-sync on a group. When I have gnus-sync'd for a while things
SB> have been stable, or at least: seemingly stable.
SB> But when I "lost" gnus-sync during the .authinfo changing around last
SB> week, I've lost read marks from back to the time when I first started
SB> gnus-sync'ing.
SB> The marks that are left are, I think, those that have been set on
SB> exactly that gnus, and residing in that gnus' .newsrc.eld.
SB> I've been stepping through the gnus-sync merge logic, but that didn't
SB> make me any wiser. What I understood seemed to operate as expected to
SB> me, if I remember correctly (it's been a while).
Yeah, this is something screwy with Gnus itself.
Ted
next prev parent reply other threads:[~2011-02-23 14:32 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 12:21 Ted Zlatanov
2011-02-23 13:45 ` Steinar Bang
2011-02-23 14:32 ` Ted Zlatanov [this message]
2011-02-24 7:37 ` Steinar Bang
2011-02-24 16:31 ` Ted Zlatanov
2011-02-24 17:34 ` Steinar Bang
2011-02-24 17:47 ` cloudy Gnus (was: nntp marks getting reset all the time) Ted Zlatanov
2011-03-11 19:47 ` cloudy Gnus Ted Zlatanov
2011-03-15 15:54 ` Lars Magne Ingebrigtsen
2011-03-15 16:02 ` Ted Zlatanov
2011-03-15 16:11 ` Lars Magne Ingebrigtsen
2011-03-15 16:25 ` Ted Zlatanov
2011-03-15 16:33 ` Lars Magne Ingebrigtsen
2011-03-17 8:49 ` Steinar Bang
2011-03-15 16:59 ` Didier Verna
2011-03-15 17:02 ` Lars Magne Ingebrigtsen
2011-03-15 17:09 ` Adam Sjøgren
2011-03-15 17:21 ` Lars Magne Ingebrigtsen
2011-03-16 8:15 ` Didier Verna
2011-03-16 13:58 ` Ted Zlatanov
2011-03-16 17:30 ` Lars Magne Ingebrigtsen
2011-03-16 19:57 ` Frank Schmitt
2011-03-17 11:03 ` Didier Verna
2011-03-15 17:17 ` Ted Zlatanov
2011-03-15 17:23 ` Lars Magne Ingebrigtsen
2011-03-25 8:17 ` Steinar Bang
2011-03-25 19:31 ` Ted Zlatanov
2011-03-25 21:45 ` Steinar Bang
2011-03-26 20:53 ` Bernt Hansen
2011-03-27 17:12 ` Steinar Bang
2011-03-27 18:35 ` Steinar Bang
2011-02-25 3:01 ` nntp marks getting reset all the time Lars Ingebrigtsen
2011-02-25 14:45 ` Ted Zlatanov
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=8762saq0t3.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).