1 Return-Path: <servilio@gmail.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 98111431FD9
\r
6 for <notmuch@notmuchmail.org>; Thu, 28 Jan 2010 04:32:53 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.649 tagged_above=-999 required=5
\r
12 tests=[AWL=-0.650, 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 zRY1ccfqhzEm for <notmuch@notmuchmail.org>;
\r
16 Thu, 28 Jan 2010 04:32:52 -0800 (PST)
\r
17 Received: from mail-ew0-f215.google.com (mail-ew0-f215.google.com
\r
19 by olra.theworths.org (Postfix) with ESMTP id 6F520431FD5
\r
20 for <notmuch@notmuchmail.org>; Thu, 28 Jan 2010 04:32:52 -0800 (PST)
\r
21 Received: by ewy7 with SMTP id 7so673867ewy.30
\r
22 for <notmuch@notmuchmail.org>; Thu, 28 Jan 2010 04:32:51 -0800 (PST)
\r
23 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
\r
24 h=domainkey-signature:mime-version:received:in-reply-to:references
\r
25 :date:message-id:subject:from:to:content-type
\r
26 :content-transfer-encoding;
\r
27 bh=muZT5743+8GhnPBDb4Z0id2P8gB+Edzz9AwxzQUBJHw=;
\r
28 b=b9/myOhqvAWJmbrp3cnO6Bfuk8sS75bBeVaGsS4Q2fvowh1jVpJkvs/Qn3qgBDKwLI
\r
29 CeBtP+YEwusrLlGWrLiwe5dFqrVVrzPcD9wzaY57XDagEQEi4EQgEWhiDVfoB6suJXoQ
\r
30 K0bdTFyl86n7p6vx0v+NjfmdMFiA+Jmr8n2xQ=
\r
31 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
\r
32 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
\r
33 :content-type:content-transfer-encoding;
\r
34 b=FnrvTbt7u0fQ/Jz8Utpw9w0AGYGL9Vibse35VR8r+YNYBF1KnS65q3CX9r7vNL4UQr
\r
35 RZ+8ZllL25noRYB0z1XxUqpW73a4PUZ9P4VSpcpP6tHjMqn43bRoKSlOh7YI+516NS2Q
\r
36 BTiy8s1Wm092uorTb/h5RfQHollNSzgFzNpSQ=
\r
38 Received: by 10.216.87.9 with SMTP id x9mr442005wee.0.1264681971294; Thu, 28
\r
39 Jan 2010 04:32:51 -0800 (PST)
\r
40 In-Reply-To: <20100128051057.GA12540@lapse.rw.madduck.net>
\r
41 References: <20100125162247.85F0F66FA8@aether.pioto.org>
\r
42 <87tyu9dfhs.fsf@servo.finestructure.net>
\r
43 <20100128051057.GA12540@lapse.rw.madduck.net>
\r
44 Date: Thu, 28 Jan 2010 07:32:51 -0500
\r
45 Message-ID: <b22065d01001280432k55b627c1hb6405985f022e9cf@mail.gmail.com>
\r
46 From: Servilio Afre Puentes <servilio@gmail.com>
\r
47 To: Jameson Rollins <jrollins@finestructure.net>,
\r
48 Mike Kelly <pioto@pioto.org>, notmuch <notmuch@notmuchmail.org>
\r
49 Content-Type: text/plain; charset=ISO-8859-1
\r
50 Content-Transfer-Encoding: quoted-printable
\r
51 Subject: Re: [notmuch] tag dir proposal [was: Re: Git as notmuch object
\r
53 X-BeenThere: notmuch@notmuchmail.org
\r
54 X-Mailman-Version: 2.1.13
\r
56 List-Id: "Use and development of the notmuch mail system."
\r
57 <notmuch.notmuchmail.org>
\r
58 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
59 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
60 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
61 List-Post: <mailto:notmuch@notmuchmail.org>
\r
62 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
63 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
65 X-List-Received-Date: Thu, 28 Jan 2010 12:32:53 -0000
\r
67 2010/1/28 martin f krafft <madduck@madduck.net>:
\r
68 > also sprach Jameson Rollins <jrollins@finestructure.net> [2010.01.26.1046=
\r
70 >> > For example, I might have:
\r
72 >> > ~/.notmuch-config:
\r
74 >> > =A0 =A0 [database]
\r
75 >> > =A0 =A0 path=3D/home/pioto/mail
\r
78 >> > =A0 =A0 pioto@pioto.org/INBOX.ListMail.notmuch =3D notmuch
\r
80 >> > So, a 'tags' section, where each key is the folder name, relative to t=
\r
82 >> > db path, and the value is one or more tag names
\r
84 >> I think this idea is a really good one and I would like to pursue it as
\r
85 >> a tangent thread here. =A0I was going to propose something very similar =
\r
87 >> this. =A0I think it's a very flexible idea that would help in a lot of
\r
90 > I think we need to carefully distinguish here. The above seems to
\r
91 > suggest a mapping from folder to tag, but we don't actually need
\r
92 > tags for folder locations because those can (and should) be implicitly
\r
93 > determined from the database
\r
95 I think that the usefulness of this functionality is that we can have
\r
96 a mapping from physical organization of the mail to a tagging scheme
\r
97 of our choosing, and we can be relieved from having to remember the
\r
98 location of the mail (that can be different in different from
\r
99 different mail clients).
\r
101 But even right now I can't find a documented way of searching by
\r
102 location, so AFAIK the implementation of this proposal would allow
\r
103 something that is not possible at the moment.
\r
106 >> inbox =3D +inbox,+unread
\r
108 >> drafts =3D +draft
\r
109 >> archive =3D -inbox
\r
111 > This proposal, on the other hand, is an interesting one, but when is
\r
112 > it supposed to happen? It just feels wrong to make this happen as
\r
113 > part of 'notmuch new'.
\r
117 > What I would like to see is a notmuch-aware MDA, e.g. a programme
\r
118 > which reads an incoming mail on stdin and can do all this kind of
\r
119 > stuff, e.g. assign tags based on such rules (or take tags as
\r
120 > arguments, so that I could trivially set tags from procmail too),
\r
121 > write the message to the message store, and update the database.
\r
123 Such an MDA wouldn't need to use "notmuch new", and thus won't be
\r
126 > This would allow us to get rid of 'notmuch new' altogether, at least
\r
127 > conceptually. We'd still need it if mail is being delivered
\r
128 > independently, e.g. with offlineimap.
\r
130 Then we'd still need it, why not make it better?
\r
projects / notmuch-archives.git / blob