From: Bob Newell <bobnewell@bobnewell.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Strange article sorting from Gmail
Date: Thu, 19 Oct 2023 11:54:22 -1000 [thread overview]
Message-ID: <87wmviffch.sftc@vgqdokvq.lyrdyko.com> (raw)
In-Reply-To: <87leby8lha.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 19 Oct 2023 12:23:45 -0700")
> Well that sounds very annoying! I suppose you already tried "M-g" to
> request a new scan of this group in particular?
Sure did, and even went to the extreme of temporarily nuking
.newsrc.eld to force a complete rebuild of the group. No
luck. The fault is clearly on the gmail side. And of course
as mentioned if I load ALL the headers into gnus, gnus then
sorts by date as expected. However I'm not thrilled about
loading 28,000 headers during each gnus session.
> I do wish I understood what Gmail is doing there, to reset the article
> numbers, and if there were anything Gnus could do automatically to
> handle it more gracefully.
It has never happened before. Something evidently triggered
it but I think it will forever remain a mystery. I did search
around for a way to make gmail's IMAP fix the numbering by
renumbering everything by date, but so far I've not found a
way to do that. (Well, there actually is. I could download
all 28,000 emails --- not just the headers but the full text
and all the mime parts --- then delete everything from the
server, then restore everything by uploading all 28,000
messages. I lack the courage, though.)
--
Bob Newell
Honolulu, Hawai`i
- Via GNU/Linux/Emacs/Gnus/BBDB
prev parent reply other threads:[~2023-10-19 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 20:04 Bob Newell
2023-10-19 19:23 ` Eric Abrahamsen
2023-10-19 21:54 ` Bob Newell [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=87wmviffch.sftc@vgqdokvq.lyrdyko.com \
--to=bobnewell@bobnewell.net \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).