From: Vincent Bernat <bernat@luffy.cx>
To: ding@gnus.org
Subject: Re: Unable to get all messages in an IMAP group
Date: Tue, 03 Feb 2015 21:52:55 +0100 [thread overview]
Message-ID: <m3fvamzpi0.fsf@neo.luffy.cx> (raw)
In-Reply-To: <upzca90vfeo7.fsf@dod.no> (Steinar Bang's message of "Tue, 03 Feb 2015 11:54:48 +0100")
❦ 3 février 2015 11:54 +0100, Steinar Bang <sb@dod.no> :
>> I'll try tonight. On my laptop, there is no such problem (same
>> newsrc.eld). It should be related to those out-of-sync UID.
>
> One other possibility:
>
> Go back to the previous version of gnus in git, and if that works, use
> git bisect to find the commit where the change happened.
>
> (If going back to the previous version of gnus doesn't help, then this
> approach won't work, obviously...)
So, it's easy to fix by going back. I have bisected (and ensured to not
fix the situation by not saving .newsrc.eld) and found that the problem
is this commit:
https://github.com/emacsmirror/gnus/commit/447c56af7cb2afac14a0f3ed23f85d907c443a5d
Before this commit, if I enter the group, I don't see all the messages
but if I hit M-g on the group, then enter it, everything is here (which
is what I expect). With this commit, doing M-g still gives an incomplete
view of the group.
--
Use uniform input formats.
- The Elements of Programming Style (Kernighan & Plauger)
next prev parent reply other threads:[~2015-02-03 20:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 23:18 Vincent Bernat
2015-02-03 6:42 ` Steinar Bang
2015-02-03 7:40 ` Vincent Bernat
2015-02-03 7:44 ` Vincent Bernat
2015-02-03 8:05 ` Steinar Bang
2015-02-03 8:17 ` Tassilo Horn
2015-02-03 9:09 ` Vincent Bernat
2015-02-03 10:54 ` Steinar Bang
2015-02-03 20:52 ` Vincent Bernat [this message]
2015-02-04 6:28 ` Steinar Bang
2015-02-04 20:48 ` Vincent Bernat
2015-02-04 21:10 ` Steinar Bang
2015-02-04 21:11 ` Vincent Bernat
2015-02-04 21:19 ` Vincent Bernat
2015-02-04 21:35 ` Vincent Bernat
2015-02-05 3:10 ` Lars Ingebrigtsen
2015-02-05 6:27 ` Vincent Bernat
2015-02-05 3:06 ` Lars Ingebrigtsen
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=m3fvamzpi0.fsf@neo.luffy.cx \
--to=bernat@luffy.cx \
--cc=ding@gnus.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).