From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25126@debbugs.gnu.org
Subject: bug#25126: 26.0.50; Gnus reacts poorly to email flags being changed behind its back
Date: Fri, 27 Sep 2019 17:15:42 -0700 [thread overview]
Message-ID: <87lfu9nump.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8736ghitze.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 27 Sep 2019 18:28:37 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Glenn Morris <rgm@gnu.org> writes:
>
>> The example in the OP is about nnmaildir.
>>
>> I don't think the details are relevant, but it happens to be being
>> synced from imap by an external process. For example, a maildir file
>> might change name from "stuff:2,S" to "stuff:2,RS" if you reply to the
>> message via an imap client. Or it could have been moved to a different
>> folder, or deleted altogether. It's not obvious to me what Gnus could do
>> in this situation.
>
> Ah, thanks for the explanation.
>
>> I imagine you could reproduce it by visiting a Maildir with Gnus, then
>> renaming one of the files externally.
>
> I don't have any maildir dirs, which probably explains why all the
> nnmaildir bug reports are languishing. Could you pack up a simple one
> and mail it to me as a tar file?
I won't keep on with this, but the gnus-mock package in ELPA will give
you a clean, reproducible Gnus installation with a maildir server that
you can use for testing. I promise I'll shut up about it after this :)
next prev parent reply other threads:[~2019-09-28 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 20:14 bug#25126: 26.0.50; Gnus reacts poorly to email flags being changed behind its back Daniel Colascione
2018-04-11 22:44 ` Lars Ingebrigtsen
2019-09-26 22:50 ` Lars Ingebrigtsen
2019-09-27 16:20 ` Glenn Morris
2019-09-27 16:28 ` Lars Ingebrigtsen
2019-09-27 17:36 ` Glenn Morris
2019-09-28 0:15 ` Eric Abrahamsen [this message]
2019-09-30 5:49 ` Lars Ingebrigtsen
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=87lfu9nump.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=25126@debbugs.gnu.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.
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.