From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: Emacs trunk and Gnus master are fully sync'd now
Date: Tue, 09 Jul 2013 15:39:29 -0400 [thread overview]
Message-ID: <87txk3tte6.fsf@lifelogs.com> (raw)
In-Reply-To: <874nc3o7ej.fsf@randomsample.de>
On Tue, 09 Jul 2013 21:33:24 +0200 David Engster <deng@randomsample.de> wrote:
DE> Giorgos Keramidas writes:
>> So the unexist ranges *are* there. But as you said the information
>> seems to be lost somewhere between the time `.newsrc.eld' loads and the
>> time Gnus queries the imap server for group state.
DE> Yes, and I found the problem. I could not reproduce this initially
DE> because it only exists in Emacs trunk, not in Gnus git. After I switched
DE> to Emacs trunk, I saw the same thing.
DE> It's actually really simple: The problem is `gnus-clean-old-newsrc',
DE> where 'unexist' marks will be removed when you upgrade from an older
DE> Gnus version, probably because the format has changed. However, in Emacs
DE> trunk, `gnus-newsrc-file-version' is "Gnus v5.13", which is always
DE> considered *smaller* than "Ma Gnus v0.03", so it will always remove the
DE> marks:
DE> (when (or force
DE> (< (gnus-continuum-version gnus-newsrc-file-version)
DE> (gnus-continuum-version "Ma Gnus v0.03")))
DE> ;; Remove old `exist' marks from old nnimap groups.
DE> So this has to be changed or maybe completely removed. I'm not sure; I
DE> guess it *could* happen that someone running Ma Gnus v0.02 upgrades to
DE> Gnus from Emacs 24.4.
DE> Katsumi? Lars? Anybody?
It seems safest to always remove old exist/unexist/whatever marks that
can be recreated from the server if `gnus-newsrc-file-version' does not
equal the current Gnus version. With a message saying why, and maybe a
way to disable it selectively and trigger it explicitly. Worst case,
some users have to download things twice... but the logic is much
simpler regarding versions.
Ted
next prev parent reply other threads:[~2013-07-09 19:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 10:40 Katsumi Yamaoka
2013-07-02 16:52 ` Giorgos Keramidas
2013-07-06 15:21 ` Lars Ingebrigtsen
2013-07-06 15:44 ` David Engster
2013-07-06 18:45 ` David Engster
2013-07-06 20:03 ` David Engster
2013-07-07 13:27 ` Giorgos Keramidas
2013-07-07 13:24 ` Giorgos Keramidas
2013-07-07 19:51 ` David Engster
2013-07-08 13:16 ` Giorgos Keramidas
2013-07-08 18:24 ` David Engster
2013-07-09 11:08 ` Giorgos Keramidas
2013-07-09 15:34 ` David Engster
2013-07-09 18:16 ` Giorgos Keramidas
2013-07-09 19:33 ` David Engster
2013-07-09 19:39 ` Ted Zlatanov [this message]
2013-07-09 20:41 ` Giorgos Keramidas
2013-07-09 21:42 ` David Engster
2013-07-10 15:32 ` Ted Zlatanov
2013-07-10 19:17 ` David Engster
2013-07-11 17:12 ` Giorgos Keramidas
2013-07-18 13:31 ` Lars Magne Ingebrigtsen
2013-07-18 15:42 ` Giorgos Keramidas
2013-07-18 16:55 ` David Engster
2013-07-18 17:15 ` Giorgos Keramidas
2013-07-30 14:56 ` Lars Magne Ingebrigtsen
2013-07-30 19:58 ` Giorgos Keramidas
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=87txk3tte6.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).