unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Sean Whitton <spwhitton@spwhitton.name>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Cc: Case Duckworth <acdw@acdw.net>
Subject: Re: Forcing a sync of maildir flags?
Date: Mon, 04 Apr 2022 21:48:53 -0700	[thread overview]
Message-ID: <87y20k9lu2.fsf@athena.silentflame.com> (raw)
In-Reply-To: <878rt122nj.fsf@melete.silentflame.com>

Hello,

On Tue 22 Mar 2022 at 12:44pm -07, Sean Whitton wrote:

> I am seeing this bug, or a closely related one, a whole lot right now.
> Messages are coming back as unread over and over again.  I recently made
> some changes to my notmuch cronjobs, so that probably has something to
> do with it, but I have no guesses as to what the problem is.
>
> As a first thing to try, I am going to add something to my pre-new hook
> to perform the new/ -> cur/ move as specified by maildir(5) on all my
> synced maildirs, so that notmuch never sees messages in new/ except when
> it writes new drafts and sent mail there (and they'll get moved on the
> next sync).
>
> I'll drop the 'notmuch tag -unread -- folder:sent' workaround at the
> same time to see what happens.

Seems to be working well.

-- 
Sean Whitton

  reply	other threads:[~2022-04-05  4:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20  4:58 Forcing a sync of maildir flags? Sean Whitton
2020-02-20 12:22 ` David Bremner
2020-02-20 13:21   ` David Bremner
2020-02-20 21:19   ` Sean Whitton
2020-02-21  0:06     ` David Bremner
2020-02-21 19:54       ` Sean Whitton
2022-05-01 23:23         ` David Bremner
2022-05-02 23:24           ` Sean Whitton
2022-05-03 12:14             ` David Bremner
2022-05-03 23:59               ` Sean Whitton
2022-03-22 19:44   ` Sean Whitton
2022-04-05  4:48     ` Sean Whitton [this message]
2022-04-13 10:27       ` Gregor Zattler

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87y20k9lu2.fsf@athena.silentflame.com \
    --to=spwhitton@spwhitton.name \
    --cc=acdw@acdw.net \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).