1 Return-Path: <too@iki.fi>
\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 A901F431FAF
\r
6 for <notmuch@notmuchmail.org>; Sat, 21 Jan 2012 12:23:59 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\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 IpkkAaiLVmYi for <notmuch@notmuchmail.org>;
\r
16 Sat, 21 Jan 2012 12:23:59 -0800 (PST)
\r
17 Received: from guru.guru-group.fi (guru-group.fi [87.108.86.66])
\r
18 by olra.theworths.org (Postfix) with ESMTP id DAFD5431FAE
\r
19 for <notmuch@notmuchmail.org>; Sat, 21 Jan 2012 12:23:58 -0800 (PST)
\r
20 Received: by guru.guru-group.fi (Postfix, from userid 501)
\r
21 id C23C768056; Sat, 21 Jan 2012 22:23:59 +0200 (EET)
\r
22 From: Tomi Ollila <tomi.ollila@iki.fi>
\r
23 To: Austin Clements <amdragon@MIT.EDU>
\r
24 Subject: Re: [PATCH] lib: Save filenames for files detected as "not an email
\r
25 file" in the database.
\r
26 In-Reply-To: <20120121181307.GI16740@mit.edu>
\r
27 References: <1327096827-5760-1-git-send-email-amdragon@mit.edu>
\r
28 <m2k44lfksv.fsf@guru.guru-group.fi>
\r
29 <20120121181307.GI16740@mit.edu>
\r
30 User-Agent: Notmuch/0.11+71~gefa5d6c (http://notmuchmail.org) Emacs/23.3.1
\r
31 (x86_64-unknown-linux-gnu)
\r
32 X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
\r
33 $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
\r
34 !)g;OY^,BjTbr)Np:%c_o'jj,Z
\r
35 Date: Sat, 21 Jan 2012 22:23:59 +0200
\r
36 Message-ID: <m2hazo6bz4.fsf@guru.guru-group.fi>
\r
38 Content-Type: text/plain; charset=us-ascii
\r
39 Cc: notmuch@notmuchmail.org
\r
40 X-BeenThere: notmuch@notmuchmail.org
\r
41 X-Mailman-Version: 2.1.13
\r
43 List-Id: "Use and development of the notmuch mail system."
\r
44 <notmuch.notmuchmail.org>
\r
45 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
46 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
47 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
48 List-Post: <mailto:notmuch@notmuchmail.org>
\r
49 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
50 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
51 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
52 X-List-Received-Date: Sat, 21 Jan 2012 20:23:59 -0000
\r
54 On Sat, 21 Jan 2012 13:13:07 -0500, Austin Clements <amdragon@MIT.EDU> wrote:
\r
55 > Quoth Tomi Ollila on Jan 21 at 11:48 am:
\r
56 > > On Fri, 20 Jan 2012 17:00:27 -0500, Austin Clements <amdragon@MIT.EDU> wrot> >
\r
57 > > > -large so the detection could be potentially slow). 2. A "notmuch
\r
58 > > > -search" syntax could be added to allow the user to find these files,
\r
59 > > > -(and perhaps delete them or move them away as appropriate).
\r
60 > > > +Add a "notmuch search" syntax to allow uses to find files recorded as
\r
61 > > > +non-emails in the database (and perhaps delete them or move them away
\r
62 > > > +as appropriate).
\r
64 > > Could these messages be tagged with some fixed tag -- we already have
\r
65 > > 'signed' and 'attachment' tag. maybe 'nonemail' (or something) could
\r
66 > > be used for these messages ?
\r
68 > They aren't actually messages. Messages have a lot of basic metadata
\r
69 > that non-email files don't have, so I went with distinct types of
\r
70 > documents, figuring that would be much less disruptive than having to
\r
71 > deal with message objects that don't support most message methods.
\r
72 > For example, if there were a tag (or any general way to query this),
\r
73 > it's unclear what the output of
\r
74 > notmuch search --output=summary tag:nonemail
\r
77 yes, I started to think all these issues *after* sending that email.
\r
78 bunch on extra if's to the code and so on; better think something
\r
81 > This isn't necessarily the right approach, but if non-emails *are*
\r
82 > represented as messages, I'm not sure what to do with things like
\r
83 > notmuch_message_get_message_id and notmuch_message_get_thread_id or
\r
84 > how to maintain backwards compatibility for callers that don't expect
\r
85 > queries to return non-emails.
\r