unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
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 12:20:27 -0400	[thread overview]
Message-ID: <jwblv590dw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87blv6fzad.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 27 Sep 2019 00:50:02 +0200")

Lars Ingebrigtsen wrote:

> So I have to ask again -- what Gnus backend is this about, and what are
> the error messages?

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.

I imagine you could reproduce it by visiting a Maildir with Gnus, then
renaming one of the files externally.

I imagine none of the Gnus backends (except imap) are prepared for files
to be renamed by other processes while Gnus is running?






  reply	other threads:[~2019-09-27 16:20 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 [this message]
2019-09-27 16:28       ` Lars Ingebrigtsen
2019-09-27 17:36         ` Glenn Morris
2019-09-28  0:15         ` Eric Abrahamsen
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwblv590dw.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).