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: Sun, 07 Jul 2013 15:27:27 +0200 [thread overview]
Message-ID: <67um8rk3l233gg.fsf@saturn.laptop> (raw)
In-Reply-To: <87hag74fsz.fsf@randomsample.de> (David Engster's message of "Sat, 06 Jul 2013 22:03:08 +0200")
On Sat, 06 Jul 2013 22:03:08 +0200, David Engster <deng@randomsample.de> wrote:
> David Engster writes:
>> David Engster writes:
>>> 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.
>>
>> Never mind; I can reproduce it with my Gmail account. I'll try to debug
>> this.
>
> It was just one bogus group called '[Google Mail]' which for some reason
> was auto-subscribed but does not really exist on the server. Otherwise,
> I cannot see that real groups get constantly recynced.
>
> So the question remains whether this only happens upon Gnus startup; if
> so, it seems that not all information gets properly saved in newsrc.eld.
In the Gnus version of the emacs-24 branch this happens with the bogus
'[Gmail]' group which Gmail advertizes too. It doesn't exist as a
group, so every time Gnus tries to do an 'initial sync'. I solved that
a few days ago by actually *creating* a group called ['Gmail]' from
within Gnus and then setting it to 'show only if unread' in Gmail's web
interface. Since it's a valid group now, Gnus doesn't do an 'initial'
sync for this group every time it starts.
In the trunk of Emacs, Gnus does an 'initial sync' for all groups, so I
suspect something is not saved properly in .newsrc.eld.
next prev parent reply other threads:[~2013-07-07 13:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 10:40 Emacs trunk and Gnus master are fully sync'd now 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67um8rk3l233gg.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).