Gnus development mailing list
 help / color / mirror / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: "Jorge A. Alfaro-Murillo" <jorge.alfaro-murillo@yale.edu>,
	Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Sometimes, gnus-summary-insert-old-articles doesn't., Re: Sometimes, gnus-summary-insert-old-articles doesn't.
Date: Tue, 05 Jun 2018 21:17:19 -0700	[thread overview]
Message-ID: <87in6wpn00.fsf@gmail.com> (raw)
In-Reply-To: <87y3ftdnz0.fsf@yale.edu> (Jorge A. Alfaro-Murillo's message of "Tue, 05 Jun 2018 15:37:07 -0400, Tue, 05 Jun 2018 12:44:19 -0700")

[-- Attachment #1: Type: text/plain, Size: 1438 bytes --]

Hi Jorge and Eric,

Thanks for the feedback!  I'm glad to know I'm not the only one.

"Jorge A. Alfaro-Murillo" <jorge.alfaro-murillo@yale.edu> writes:

> Andreas Schwab writes:
>
>> On Jun 04 2018, Chris Marusich <cmmarusich@gmail.com> wrote: 
>>
>>> Is it normal for gnus-summary-insert-old-articles to add no
>>> articles to the summary buffer even though it says that some old
>>> articles are available? 
>>
>> Perhaps due to gaps in the article numbers.
>
> Yeah, that happens to me with gmail. I think that the numbers are the
> ones in "All Mail", that is why there are gaps in "Inbox" or other
> folders.

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> It does look like `gnus-summary-insert-old-articles' calculates the old
> article numbers to request without consulting the backend.

How might I begin to troubleshoot to see if this is a bug on Gmail's
side, within my local Gnus configuration, or within Gnus itself?  I'm
mainly just curious, since like I said I can just request arbitrarily
many articles to eventually get the older ones.

I've noticed this behavior occurs not only with Gmail but also with
other IMAP email providers, as well.  Anecdotally, today I observed
using a non-Gmail IMAP service that when I requested 10 old articles, I
got less than 10, and when I requested 10 again, I got even more
articles (but still less than 10).  It's quite curious.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-06-06  4:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05  6:56 Chris Marusich
2018-06-05  9:32 ` Eric S Fraga
2018-06-05 18:55 ` Andreas Schwab
2018-06-05 19:37   ` Jorge A. Alfaro-Murillo
2018-06-06  4:17     ` Chris Marusich [this message]
2018-06-06 16:53       ` Sometimes, gnus-summary-insert-old-articles doesn't., " Eric Abrahamsen
2018-06-09 10:01         ` Eric S Fraga
2018-06-09 16:17           ` Eric Abrahamsen
2018-06-05 19:44   ` Eric Abrahamsen

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=87in6wpn00.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    --cc=jorge.alfaro-murillo@yale.edu \
    /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).