From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id AEE566DE0E8B for ; Thu, 20 Feb 2020 05:21:39 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.067 X-Spam-Level: X-Spam-Status: No, score=-0.067 tagged_above=-999 required=5 tests=[AWL=-0.066, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30YnWUEcNn1I for ; Thu, 20 Feb 2020 05:21:39 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id DBACB6DE024F for ; Thu, 20 Feb 2020 05:21:38 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1j4llq-0004ii-2Y; Thu, 20 Feb 2020 08:21:38 -0500 Received: (nullmailer pid 302505 invoked by uid 1000); Thu, 20 Feb 2020 13:21:36 -0000 From: David Bremner To: Sean Whitton , notmuch@notmuchmail.org Subject: Re: Forcing a sync of maildir flags? In-Reply-To: <87r1ypsb1p.fsf@tethera.net> References: <871rqp97o0.fsf@iris.silentflame.com> <87r1ypsb1p.fsf@tethera.net> Date: Thu, 20 Feb 2020 09:21:36 -0400 Message-ID: <87k14hs8bj.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Feb 2020 13:21:39 -0000 David Bremner writes: >> This works: >> >> notmuch tag +unread -- folder:sent >> notmuch tag -unread -- folder:sent >> >> Is there some more elegant way to force a sync of maildir flags? Am I >> the only one that has copies of my own mail in my inbox folder, not >> marked as read from the point of view of anything except notmuch? > > I guess my workflow doesn't expose this problem as I leave many messages > unread (relying on the inbox flag). I'm not sure about the locking > implications, but having sent messages delivered to cur/ instead of to > new/ would probably workaround the problem. I guess the other thing is that I have [new] tags=unread;inbox;new in .notmuch-config, which means that "notmuch new" moves things into cur/. Maybe you can use that effect? d