1 Return-Path: <k@ilowiecki.com>
\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 44F7F431FD0
\r
6 for <notmuch@notmuchmail.org>; Sun, 18 Dec 2011 15:02:38 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.507 tagged_above=-999 required=5
\r
12 tests=[MISSING_HEADERS=1.207, RCVD_IN_DNSWL_LOW=-0.7]
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id G6GH0ASPJcXI for <notmuch@notmuchmail.org>;
\r
17 Sun, 18 Dec 2011 15:02:37 -0800 (PST)
\r
18 Received: from mail-gx0-f181.google.com (mail-gx0-f181.google.com
\r
19 [209.85.161.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id A7D06431FB6
\r
22 for <notmuch@notmuchmail.org>; Sun, 18 Dec 2011 15:02:37 -0800 (PST)
\r
23 Received: by ggnr5 with SMTP id r5so4348580ggn.26
\r
24 for <notmuch@notmuchmail.org>; Sun, 18 Dec 2011 15:02:36 -0800 (PST)
\r
25 Received: by 10.100.86.11 with SMTP id j11mr7465263anb.23.1324249355988;
\r
26 Sun, 18 Dec 2011 15:02:35 -0800 (PST)
\r
27 Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com
\r
29 by mx.google.com with ESMTPS id i4sm26302899yhk.21.2011.12.18.15.02.34
\r
30 (version=SSLv3 cipher=OTHER); Sun, 18 Dec 2011 15:02:34 -0800 (PST)
\r
31 Received: by qcha6 with SMTP id a6so3537246qch.26
\r
32 for <notmuch@notmuchmail.org>; Sun, 18 Dec 2011 15:02:33 -0800 (PST)
\r
34 Received: by 10.224.40.10 with SMTP id i10mr21924198qae.82.1324249353621; Sun,
\r
35 18 Dec 2011 15:02:33 -0800 (PST)
\r
36 Received: by 10.229.83.201 with HTTP; Sun, 18 Dec 2011 15:02:33 -0800 (PST)
\r
37 In-Reply-To: <4eee3fe5.8bcbe30a.6d78.1918@mx.google.com>
\r
39 <CANcQd8POazwALwAodK=hnaD7OyxhJD_awJ+J-f0+Ek8_0yNEMA@mail.gmail.com>
\r
40 <4eee3fe5.8bcbe30a.6d78.1918@mx.google.com>
\r
41 Date: Mon, 19 Dec 2011 00:02:33 +0100
\r
43 <CANcQd8OV0dQC-4Tq=+gxNVySTf8vqOO7HSJSOYqZsO2coU1YrQ@mail.gmail.com>
\r
44 Subject: Re: [alot] Introducing myself, asking various questions
\r
45 From: Krzysztof Ilowiecki <k@ilowiecki.com>
\r
46 Cc: notmuch@notmuchmail.org
\r
47 Content-Type: text/plain; charset=UTF-8
\r
48 X-BeenThere: notmuch@notmuchmail.org
\r
49 X-Mailman-Version: 2.1.13
\r
51 List-Id: "Use and development of the notmuch mail system."
\r
52 <notmuch.notmuchmail.org>
\r
53 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
54 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
55 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
56 List-Post: <mailto:notmuch@notmuchmail.org>
\r
57 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
58 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
59 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
60 X-List-Received-Date: Sun, 18 Dec 2011 23:02:38 -0000
\r
62 On Sun, Dec 18, 2011 at 20:32, Patrick Totzke
\r
63 <patricktotzke@googlemail.com> wrote:
\r
64 > If you're interested: Sebastian (spaetz) is looking for
\r
65 > a replacement to fork on the python bindings to libnotmuch.
\r
66 > A rewrite in cython would be great.
\r
68 I'll have a look, but I've never tried cython and this sounds like
\r
69 someone more experienced would be preferred.
\r
71 > I guess most of us use offlineimap or getmail in combination
\r
72 > with notmuch. And Debian is also popular choice afaik,
\r
73 I was going to use getmail, but alot docs nudged me towards offlineimap
\r
76 >>How likely is it to mess things up in IMAP?
\r
77 > It being offlineimap? dependss on your config but I have no trouble
\r
80 It being the whole stack, mainly alot - i.e. some bug that would mess up
\r
81 the local copy which then would get synced up imap. I think I'm going to
\r
82 try it with a live account anyway:)
\r
84 >>I understand synchronisation across machines and with IMAP is something
\r
85 >>of an issue so far. How bad would it be to use git for that - and for
\r
86 >>'undo'? It would appear some people use git+maildir even instead of
\r
87 >>IMAP, but I guess the notmuch's database may be completely unsuitable...
\r
89 > Davd Bremner has been working on logging integration, which
\r
90 > is focused on enabling tag syncronization in future releases i believe.
\r
92 I am going to have a closer look at this. TBH it sounds a bit confusing
\r
93 how logging is related to syncing, I guess it's more like a journal
\r
94 rather than like /var/log
\r
96 > Also check out nmbug, that uses git for notmuch bugtracking.
\r
98 Does it mean it's possible to sync the database via git, which would in
\r
99 principle enable putting everything in git? I guess it is much more
\r
100 complex than it sounds, I will have a closer look.
\r
102 >>Does alot have some sort of the design documentation,
\r
103 > There are fairly complete api docs available at alot.rtfd.org
\r
105 Thank you, these are very nice api docs indeed.
\r
106 However, I meant something more like design goals, ui sketches, diagrams
\r
107 with features not necessarily implemented yet. I guess this is mostly in
\r
108 the developers' mind rather than on paper/bytes.
\r
110 >>sketched vision it is heading towards?
\r
111 > world domination, obviously :)
\r
113 oh, now I see why the diagrams are confidential :)
\r
115 >>I think I should write down my ideas before I get
\r
116 >>too entangled in the implementation details, it would be good to
\r
117 >>know if something like this is already available.
\r
118 > check out the issue tracker on https://github.com/pazz/alot/issues ,
\r
119 > I'm using github to coordinate work on alot.
\r
121 Great, this looks like a very useful issue tracker.
\r
123 Thanks alot for your reply!:)
\r
projects / notmuch-archives.git / blob