From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id EAEF5431FAE for ; Tue, 12 Mar 2013 03:24:58 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VxOKg8hspNjs for ; Tue, 12 Mar 2013 03:24:58 -0700 (PDT) Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 22DD0431FAF for ; Tue, 12 Mar 2013 03:24:57 -0700 (PDT) Received: by mail-wg0-f47.google.com with SMTP id dr13so6043782wgb.14 for ; Tue, 12 Mar 2013 03:24:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:to:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-type:x-gm-message-state; bh=qeua8fVjIU6vGhfmfOuVoJ/MbZp5LTvlL4hY6zq4DFc=; b=pmn3yl7/CeNfV6MT8neUwYfTFkZTzGj4upmsnfNHfF9dn24Y6MnPVwgodn3qDLj1jo F4WqV0fCn/TnEbknhC47f+kE9lSZThWl0FqF5mop37Jxx/RiXQ9iE3kcQFOAwA+ZI8b4 KJ+2yWNGqBGllAkeI6zxT+wr5+1j1UfV9iXJclHjzgJTVR4j7I2FC5XeKQ+ZXHzXklu2 0gJBoIEENuiakowXK15ZTHT/4GcNvpzavMnPUTMJWadeOmRQOI6reN9v17AT/szCBaNQ NmTEDAtwaR5QORj8camfFrUcPH9jF3lg6WNgEH4kZcuVxhrEorCHDXgR9RifkL5ss/c3 bZ8g== X-Received: by 10.194.62.170 with SMTP id z10mr25282289wjr.34.1363083895520; Tue, 12 Mar 2013 03:24:55 -0700 (PDT) Received: from localhost ([2001:4b98:dc0:43:216:3eff:fe1b:25f3]) by mx.google.com with ESMTPS id q13sm26317149wie.0.2013.03.12.03.24.53 (version=TLSv1.1 cipher=RC4-SHA bits=128/128); Tue, 12 Mar 2013 03:24:54 -0700 (PDT) From: Jani Nikula To: Daniel , notmuch@notmuchmail.org Subject: Re: synchronizing tag for cur/new location of mail In-Reply-To: References: User-Agent: Notmuch/0.15.2+34~ga90fdd9 (http://notmuchmail.org) Emacs/23.2.1 (x86_64-pc-linux-gnu) Date: Tue, 12 Mar 2013 11:24:44 +0100 Message-ID: <871ubkdifn.fsf@nikula.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Gm-Message-State: ALoCoQm3stsh9a5U2nVqoAAamWA6FbqjWKaKwRoyZsvKkI9tSjJvGTQGry9xhwKLswwQqF7oZRC3 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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: Tue, 12 Mar 2013 10:24:59 -0000 On Tue, 12 Mar 2013, Daniel wrote: > Is there currently no automatic tag that reflects whether a mail was > found in folder/cur or folder/new? The "unread" tag properly reflects > the maildir ",S" flag, but the one named "new" doesn't seem to be > automatic in any way, right? That's correct, there's no such automatic tag. The "new" tag is in no way special to notmuch. It's just a typically used temp tag, usually added by 'notmuch new' based on the user's new.tags config, and removed by the user's post-new hook. > I mostly use notmuch as a search backend to mutt, and it certainly is > very useful. Though since I started feeding rss to maildir, I would like > the idea of presenting somewhere in my system a list of new and "unseen" > mails (in the mutt sense, kind of, which you might be familiar with). >From notmuch perspective the difference between "new" and "cur" is just that the message files in "new" have no maildir flags set, and once maildir flags are set, they are moved to "cur". No additional semantics is applied to the file location. > Presently this seems impossible. A search for folder:new might be helpful, depending on your setup. It seems that you may get surprising results if you have more than one file with the same message-id, and some of those files are in "new" and some in "cur". (Any code to support automatic "new" tag would have to handle this too.) HTH, Jani.