1 Return-Path: <Sebastian@SSpaeth.de>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 42C6B431FBC
\r
6 for <notmuch@notmuchmail.org>; Thu, 25 Feb 2010 01:41:12 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.667 tagged_above=-999 required=5
\r
12 tests=[AWL=-0.668, BAYES_50=0.001] autolearn=ham
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id TmGO+cDaVur8 for <notmuch@notmuchmail.org>;
\r
16 Thu, 25 Feb 2010 01:41:11 -0800 (PST)
\r
17 Received: from homiemail-a23.g.dreamhost.com (caiajhbdcbhh.dreamhost.com
\r
19 by olra.theworths.org (Postfix) with ESMTP id 8675C431FAE
\r
20 for <notmuch@notmuchmail.org>; Thu, 25 Feb 2010 01:41:11 -0800 (PST)
\r
21 Received: from sspaeth.de (unknown [195.190.178.84])
\r
22 by homiemail-a23.g.dreamhost.com (Postfix) with ESMTPA id E89374B0087;
\r
23 Thu, 25 Feb 2010 01:41:00 -0800 (PST)
\r
24 Received: by sspaeth.de (sSMTP sendmail emulation);
\r
25 Thu, 25 Feb 2010 10:40:58 +0100
\r
26 From: "Sebastian Spaeth" <Sebastian@SSpaeth.de>
\r
27 To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
\r
28 In-Reply-To: <87wry2wl7p.fsf@yoom.home.cworth.org>
\r
29 References: <87pr57jvkz.fsf@SSpaeth.de> <87wry2wl7p.fsf@yoom.home.cworth.org>
\r
30 Date: Thu, 25 Feb 2010 10:40:57 +0100
\r
31 Message-ID: <87k4u1bql2.fsf@SSpaeth.de>
\r
33 Content-Type: text/plain; charset=us-ascii
\r
34 Subject: Re: [notmuch] Introducing notmuchsync
\r
35 X-BeenThere: notmuch@notmuchmail.org
\r
36 X-Mailman-Version: 2.1.13
\r
38 List-Id: "Use and development of the notmuch mail system."
\r
39 <notmuch.notmuchmail.org>
\r
40 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
41 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
42 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
43 List-Post: <mailto:notmuch@notmuchmail.org>
\r
44 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
45 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
46 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
47 X-List-Received-Date: Thu, 25 Feb 2010 09:41:12 -0000
\r
49 On Wed, 24 Feb 2010 10:19:06 -0800, Carl Worth <cworth@cworth.org> wrote:
\r
50 > On Mon, 18 Jan 2010 16:12:28 +0100, "Sebastian Spaeth" <Sebastian@SSpaeth.de> wrote:
\r
51 > > ================
\r
52 > > - Synchronizes the "S" flag with the "unread" tag (1-way). The
\r
53 > > synchronization direction is decided by using either --sync (change
\r
54 > > maildir flags according to notmuch) or --revsync (change notmuch tags
\r
55 > > according to maildir). By default it always checks the mails from the
\r
56 > > previous 30 days (but can also do --all mails if you have plenty of
\r
58 > > - Deletes all mail files that have the "delete" tag
\r
59 > > - Quiet/normal/verbose logging
\r
61 > Thanks for contributing this, Sebastian.
\r
63 No problem. It was just an itch I had :-). I have to say that I stopped
\r
64 using the --revsync (change notmuch tags based on maildir flags) as I am
\r
65 using the patch that does that from within "notmuch new" and which is
\r
66 much faster than any external script could be.
\r
68 > Let me know if you'd like to host this within the contrib directory of
\r
69 > the notmuch repository.
\r
71 I am fine with hosting it in contrib or on github whatever others
\r
74 > > - It temporarily slurps in all your mails from the last 30 days into
\r
75 > > RAM. I am waiting for "notmuchs show blah --output filename --output
\r
76 > > tags" to improve that :). Generally the parsing of the output of
\r
77 > > "notmuch show" is a bit hackyish with regexps at the moment.
\r
79 > OK. So we'll be adding an --output option to give you just filenames
\r
80 > soon, and we've got JSON output now so you can avoid hacky regexps now.
\r
82 JSON will definitely help. I need to investigate that, and --output will
\r
83 make help performance. So yes, these are good changes from a 3rd party
\r
84 perspective. I was thinking of interfacing notmuch.so directly but as
\r
85 long as the python bindings are still in development, I am not going to
\r
86 look at this option.
\r
88 > I think that's the open question still. How much of this kind of
\r
89 > functionality do we integrate into notmuch itself. I don't know the
\r
90 > answer to that question yet, but I'm quite happy to see people
\r
91 > experimenting with doing scripts like this on top of notmuch already.
\r
93 I'll comment on that in JRollins reply in a second :).
\r