From: David Engster <deng@randomsample.de>
To: keramida@ceid.upatras.gr (Giorgos Keramidas)
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Katsumi Yamaoka <yamaoka@jpl.org>,
ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Emacs trunk and Gnus master are fully sync'd now
Date: Tue, 09 Jul 2013 21:33:24 +0200 [thread overview]
Message-ID: <874nc3o7ej.fsf@randomsample.de> (raw)
In-Reply-To: <67um8rzjtvtx98.fsf@saturn.laptop> (Giorgos Keramidas's message of "Tue, 09 Jul 2013 20:16:03 +0200")
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.
Yes, and I found the problem. I could not reproduce this initially
because it only exists in Emacs trunk, not in Gnus git. After I switched
to Emacs trunk, I saw the same thing.
It's actually really simple: The problem is `gnus-clean-old-newsrc',
where 'unexist' marks will be removed when you upgrade from an older
Gnus version, probably because the format has changed. However, in Emacs
trunk, `gnus-newsrc-file-version' is "Gnus v5.13", which is always
considered *smaller* than "Ma Gnus v0.03", so it will always remove the
marks:
(when (or force
(< (gnus-continuum-version gnus-newsrc-file-version)
(gnus-continuum-version "Ma Gnus v0.03")))
;; Remove old `exist' marks from old nnimap groups.
So this has to be changed or maybe completely removed. I'm not sure; I
guess it *could* happen that someone running Ma Gnus v0.02 upgrades to
Gnus from Emacs 24.4.
Katsumi? Lars? Anybody?
-David
next prev parent reply other threads:[~2013-07-09 19:33 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 [this message]
2013-07-09 19:39 ` Ted Zlatanov
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=874nc3o7ej.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=keramida@ceid.upatras.gr \
--cc=larsi@gnus.org \
--cc=yamaoka@jpl.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).