From: Andreas Schwab <schwab@linux-m68k.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: ding@gnus.org
Subject: Re: Sometimes, gnus-summary-insert-old-articles doesn't.
Date: Tue, 05 Jun 2018 20:55:14 +0200 [thread overview]
Message-ID: <87vaaxxdv1.fsf@igel.home> (raw)
In-Reply-To: <87o9gp90wm.fsf@gmail.com> (Chris Marusich's message of "Mon, 04 Jun 2018 23:56:41 -0700")
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.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2018-06-05 18:55 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 [this message]
2018-06-05 19:37 ` Jorge A. Alfaro-Murillo
2018-06-06 4:17 ` Sometimes, gnus-summary-insert-old-articles doesn't., " Chris Marusich
2018-06-06 16:53 ` 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=87vaaxxdv1.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=cmmarusich@gmail.com \
--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).