From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Missing marks with nnimap
Date: Sat, 30 Oct 2010 13:16:31 +0200 [thread overview]
Message-ID: <m3lj5gkk1c.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <x6eib8dmxc.fsf@gmail.com>
Knut Anders Hatlen <kahatlen@gmail.com> writes:
> Found it. The server doesn't have \* in PERMANENTFLAGS. And the
> non-QRESYNC code in nnimap-update-info fails to see that \Flagged is
> supported because it checks whether (%Flagged 1012 1027 ...) is member
> of permanent-flags. So it seems it's just missing a call to car before
> calling memq. The attached patch made the problem go away for me.
Ah, right. Thanks; applied.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2010-10-30 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 11:29 Knut Anders Hatlen
2010-10-29 23:35 ` Lars Magne Ingebrigtsen
2010-10-30 8:45 ` Knut Anders Hatlen
2010-10-30 9:55 ` Knut Anders Hatlen
2010-10-30 11:16 ` Lars Magne Ingebrigtsen [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=m3lj5gkk1c.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).