Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: nnimap-get-groups: %NoSelect vs. %Noselect
Date: Mon, 22 Jul 2019 10:58:43 -0700	[thread overview]
Message-ID: <87v9vu6je4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87woge6suz.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Fri, 19 Jul 2019 15:45:08 +0200")


On 07/19/19 15:45 PM, Lars Ingebrigtsen wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> dick <dick.r.chiang@gmail.com> writes:
>>
>>> Dovecot capitalizes the no-select flag as "%Noselect" when nnimap-get-groups
>>> expects "%NoSelect".  My internal fix was to lowercase-normalize all the
>>> flags and then match on "%noselect".
>>
>> Looks like the RFCs also have %Noselect, so I expect we're just doing it
>> wrong here. I never noticed as all my Noselect groups don't actually
>> exist (they only hold children), so they were getting filtered out
>> later.
>>
>> Does anyone know of any servers that use %NoSelect? Looks like this
>> should be a straight fix, otherwise.
>
> Yup.  I have no recollection of \NoSelect, and the server I was using
> for testing at that time was Dovecot...  is it possible that they
> released a version that had \NoSelect at some point?
>
> But it's probably just a typo on my part.

I'm just going to switch this to %Noselect, I think. I'll keep an eye on
bug reports, and we can switch to a check for both, if necessary.



      parent reply	other threads:[~2019-07-22 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17  2:24 dick
2019-07-18 19:37 ` Eric Abrahamsen
2019-07-19 13:45   ` Lars Ingebrigtsen
2019-07-19 17:27     ` Eric Abrahamsen
2019-07-22 17:58     ` Eric Abrahamsen [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=87v9vu6je4.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    --cc=larsi@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).