Gnus development mailing list
 help / color / mirror / Atom feed
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Lars Magne 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: Tue, 30 Jul 2013 21:58:16 +0200	[thread overview]
Message-ID: <CAKR2__0iLKrP5=ZCen8kCRL0ns1ooiGzeohyX3aUnF4FCLzdtQ@mail.gmail.com> (raw)
In-Reply-To: <m3li4odrlb.fsf@stories.gnus.org>

On Tue, Jul 30, 2013 at 4:56 PM, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
> Giorgos Keramidas <keramida@ceid.upatras.gr> writes:
>> When I start Gnus from the Emacs trunk with the patch by David to show
>> why a group is resynchronized, I can see that some groups like INBOX with
>> no unread messages are sync'ed every time.  Typing 's' at the *Group*
>> buffer doesn't save anything, but if I type 'M-x gnus-group-save-newsrc'
>> a new .newsrc.eld file is created, and the groups do _not_ go through an
>> initial sync afterwards.
>
> It looks like the Gnus data isn't always marked as changed when you hit
> `g' on nnimap groups, so I've now made it mark stuff as changed always.
> (Which may be wrong, but should at least avoid this problem.)

Thanks! I see this change in Gnus git repository:
http://git.gnus.org/cgit/gnus.git/commit/?id=72a58393e70fa1c15e7b3e251d052e8384fcf281

I cherry-picked this into my local copy of Emacs trunk, and it worked fine!



      reply	other threads:[~2013-07-30 19:58 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
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 [this message]

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='CAKR2__0iLKrP5=ZCen8kCRL0ns1ooiGzeohyX3aUnF4FCLzdtQ@mail.gmail.com' \
    --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).