From: Lars Ingebrigtsen <larsi@gnus.org>
To: Mike Kupfer <m.kupfer@acm.org>
Cc: 22590@debbugs.gnu.org
Subject: bug#22590: 24.5; gnus/nnimap: ticked messages not getting marked as read
Date: Fri, 27 Sep 2019 01:14:41 +0200 [thread overview]
Message-ID: <871rw2fy5a.fsf@gnus.org> (raw)
In-Reply-To: <87wpdh5th7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 26 Jan 2017 23:47:32 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Mike Kupfer <m.kupfer@acm.org> writes:
>
>> - a message is unread and flagged (ticked) on the IMAP server. Gnus
>> shows it and the next message in the summary buffer as ticked. (I'm
>> not sure that status of the second message is critical for reproducing
>> the problem, but it seems to help.)
>> - in the Gnus summary buffer, I type "d" for the first message. The
>> message is marked "r" in the summary buffer, as expected.
>> - I exit the summary buffer and type "s" in the Group buffer
>> - I check the folder using Thunderbird; it shows the first message as no
>> longer flagged, but it's still shown as unread.
>
> I think I understand what's going on. In Gnus, there's no such thing as
> "ticked and unread": Everything that's \Flagged in the IMAP server
> becomes read in Gnus. So when you remove the tick (i.e., \Flagged),
> Gnus will propagate that change to the IMAP server, but since it thinks
> that nothing has changed WRT readedness, it doesn't send that
> information to the server...
>
> I'm not sure what the best way to fix that is...
I now made nnimap update readedness when tickedness changes, which I
think should do the trick.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-09-26 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-07 22:41 bug#22590: 24.5; gnus/nnimap: ticked messages not getting marked as read Mike Kupfer
2017-01-26 22:47 ` Lars Ingebrigtsen
2019-09-26 23:14 ` Lars 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=871rw2fy5a.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=22590@debbugs.gnu.org \
--cc=m.kupfer@acm.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.