From: Andrew Cohen <acohen@ust.hk>
To: info-gnus-english@gnu.org
Subject: Re: nnimap gmail "A T" and "^" not working
Date: Thu, 19 May 2022 08:00:28 +0800 [thread overview]
Message-ID: <87r14qmlwj.fsf@ust.hk> (raw)
In-Reply-To: <87r14qo9hi.fsf@ericabrahamsen.net>
Hi All:
gmail's imap implementation is non-standard and the standard
thread-referral search doesn't seem to work properly (I never noticed
this before since most of email activity is not in gmail). Although it
will take a little time I don't think it will be very hard to get it
working. As Eric said, we can special-case gmail in gnus-search and just
have to understand the details of how gmail searching works (I think I
have already worked this out but have to do some more testing).
So to the original poster jibstyle209: it's not you (and it's not gnus) it's
gmail. But we should be able to work around it.
>>>>> "EA" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
EA> JibStyle <jibstyle209@gmail.com> writes:
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> Hey there! Thanks for the report. It looks like Gmails' IMAP
>>> weirdness might be weird enough to break the thread-searching
>>> code in Gnus. I think it's definitely worth special-casing code
>>> for Gmail; give me a few days and I'll see what I can figure
>>> out.
>>
>> Thank you for investigating. Are you able to reproduce the issue?
>> I am unsure if there is a problem with Gnus <--> Gmail, or if I
>> am doing something wrong. That is why I ask how other users
>> approach nnimap gmail threading.
>>
>> My `gnus-secondary-select-methods' (primary method is nnnil):
>>
>> ((nnimap "imap.gmail.com" (nnimap-address "imap.gmail.com")
>> (nnimap-server-port 993) (nnimap-stream ssl)
>> (nnimap-split-methods default) (nnimap-inbox "INBOX")
>> (nnimap-expunge immediately) (nnmail-expiry-wait immediate))
>> (nntp "news.gmane.io"))
>>
>> Please let me know if any additional information is useful, or
>> any suggested workarounds. Thank you!
EA> I technically have a gmail account, but can't access it from
EA> Gnus, so I probably won't be able to reproduce. But it's a good
EA> idea to adapt some code specifically for Gmail anyway, so I hope
EA> to be able to provide some code to test on the list here in the
EA> next week or so.
--
Andrew Cohen
Director, HKUST Jockey Club Institute for Advanced Study
Lam Woo Foundation Professor and Chair Professor of Physics
The Hong Kong University of Science and Technology
next prev parent reply other threads:[~2022-05-19 0:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 6:14 JibStyle
2022-05-18 7:37 ` Byung-Hee HWANG
2022-05-18 19:49 ` JibStyle
2022-05-18 21:54 ` Byung-Hee HWANG
2022-05-18 16:38 ` Eric Abrahamsen
2022-05-18 20:15 ` JibStyle
2022-05-18 20:45 ` Eric Abrahamsen
2022-05-19 0:00 ` Andrew Cohen [this message]
2022-05-19 2:41 ` JibStyle
2022-05-19 5:45 ` Andrew Cohen
2022-05-19 23:19 ` JibStyle
2022-05-20 0:06 ` Andrew Cohen
2022-05-20 22:01 ` JibStyle
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=87r14qmlwj.fsf@ust.hk \
--to=acohen@ust.hk \
--cc=info-gnus-english@gnu.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).