From: keramida@ceid.upatras.gr (Giorgos Keramidas)
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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: Mon, 08 Jul 2013 15:16:20 +0200 [thread overview]
Message-ID: <67um8ry59hnqe3.fsf@saturn.laptop> (raw)
In-Reply-To: <877gh24094.fsf@randomsample.de> (David Engster's message of "Sun, 07 Jul 2013 21:51:19 +0200")
On Sun, 07 Jul 2013 21:51:19 +0200, David Engster <deng@randomsample.de> wrote:
> Giorgos Keramidas writes:
>> On Sat, 06 Jul 2013 17:44:30 +0200, David Engster <deng@randomsample.de> wrote:
>>> AFAICS in `nnimap-retrieve-group-data-early', the resync should only
>>> happen when there's either no 'active', 'unexist', or
>>> 'uidvalidity'. Perhaps the first step should be to install some verbose
>>> messaging which says which of those triggers the resync.
>>
>> I can try that. Thanks for the pointer.
>
> You can apply the attached patch against current Emacs trunk to see in
> the *Messages* buffer why a group is triggered for resync.
Thanks for this patch:
> === modified file 'lisp/gnus/nnimap.el'
> --- lisp/gnus/nnimap.el 2013-07-02 10:38:58 +0000
> +++ lisp/gnus/nnimap.el 2013-07-07 19:48:50 +0000
> @@ -1326,6 +1326,12 @@
> (if (and active uidvalidity unexist)
> ;; Fetch the last 100 flags.
> (setq start (max 1 (- (cdr active) 100)))
> + (message
> + (concat "Initial sync: Group " group
> + ". Reason: "
> + (when (not active) "active ")
> + (when (not uidvalidity) "uidvalidity ")
> + (when (not unexist) "unexist ")))
> (incf (nnimap-initial-resync nnimap-object))
> (setq start 1))
> (push (list (nnimap-send-command "%s %S" command
The messages logged point to 'unexist' for all the groups:
Reading /Users/gkeramidas/.newsrc.eld...
Opening nnfolder server on archive...done
No new newsgroups
Checking new news...
Initial sync: Group trips-2013-08-greece. Reason: unexist
Initial sync: Group mercurial-main. Reason: unexist
Initial sync: Group linkedin. Reason: unexist
Initial sync: Group tex-context. Reason: unexist
Initial sync: Group wikipedia. Reason: unexist
Initial sync: Group unix-admin-gr. Reason: unexist
Initial sync: Group twitter. Reason: unexist
Initial sync: Group trips-2011-09-zurich-ntinos-aggeliki. Reason: unexist
Initial sync: Group trips-2010-10-zurich-relocation. Reason: unexist
Initial sync: Group transifex-devel. Reason: unexist
Initial sync: Group spotify. Reason: unexist
Initial sync: Group serverhive. Reason: unexist
Initial sync: Group plug. Reason: unexist
Initial sync: Group mobility. Reason: unexist
Initial sync: Group migrate2linux. Reason: unexist
Initial sync: Group microsoft. Reason: unexist
Initial sync: Group mercurial-devel. Reason: unexist
Initial sync: Group mercurial-bug. Reason: unexist
Initial sync: Group lgu. Reason: unexist
Initial sync: Group interview. Reason: unexist
Initial sync: Group intelen. Reason: unexist
Initial sync: Group ikea. Reason: unexist
Initial sync: Group homegate. Reason: unexist
Initial sync: Group google-plus. Reason: unexist
Initial sync: Group freebsd-www. Reason: unexist
Initial sync: Group freebsd-threads. Reason: unexist
Initial sync: Group freebsd-security. Reason: unexist
Initial sync: Group freebsd-questions. Reason: unexist
Initial sync: Group freebsd-newbies. Reason: unexist
Initial sync: Group freebsd-net. Reason: unexist
Initial sync: Group freebsd-fs. Reason: unexist
Initial sync: Group freebsd-doc-el. Reason: unexist
Initial sync: Group freebsd-bugs. Reason: unexist
Initial sync: Group freebsd-announce-moderators. Reason: unexist
Initial sync: Group freebsd-advocacy. Reason: unexist
Initial sync: Group fitocracy. Reason: unexist
Initial sync: Group esr-uvc-review. Reason: unexist
Initial sync: Group emacs-devel. Reason: unexist
Initial sync: Group discus. Reason: unexist
Initial sync: Group dentist. Reason: unexist
Initial sync: Group cyanogen. Reason: unexist
Initial sync: Group bsd-gr. Reason: unexist
Initial sync: Group bitbucket-issues. Reason: unexist
Initial sync: Group bitbucket. Reason: unexist
Initial sync: Group atf-devel. Reason: unexist
Initial sync: Group atf. Reason: unexist
[...]
Does `unexist' mean that the group does not exist locally? I see a few
lines above that we check (and active uidvalidity unexist) but if
'unexist' means that the groups does not exist in `.newsrc.eld', then we
are not reading the .newsrc.eld contents correctly.
next prev parent reply other threads:[~2013-07-08 13:16 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 [this message]
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
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=67um8ry59hnqe3.fsf@saturn.laptop \
--to=keramida@ceid.upatras.gr \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--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).