1 Return-Path: <jani@nikula.org>
\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 23D8B421192
\r
6 for <notmuch@notmuchmail.org>; Wed, 29 Jun 2011 13:15:30 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\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 nS1josoN0WCx for <notmuch@notmuchmail.org>;
\r
16 Wed, 29 Jun 2011 13:15:28 -0700 (PDT)
\r
17 Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com
\r
18 [209.85.216.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id 4BFE142118E
\r
21 for <notmuch@notmuchmail.org>; Wed, 29 Jun 2011 13:15:28 -0700 (PDT)
\r
22 Received: by qyk9 with SMTP id 9so1039458qyk.5
\r
23 for <notmuch@notmuchmail.org>; Wed, 29 Jun 2011 13:15:27 -0700 (PDT)
\r
24 Received: by 10.224.140.146 with SMTP id i18mr930579qau.33.1309378527250;
\r
25 Wed, 29 Jun 2011 13:15:27 -0700 (PDT)
\r
26 Received: from localhost (nikula.org [92.243.24.172])
\r
27 by mx.google.com with ESMTPS id u15sm1156352qcq.24.2011.06.29.13.15.24
\r
28 (version=TLSv1/SSLv3 cipher=OTHER);
\r
29 Wed, 29 Jun 2011 13:15:25 -0700 (PDT)
\r
30 From: Jani Nikula <jani@nikula.org>
\r
31 To: Jameson Graef Rollins <jrollins@finestructure.net>,
\r
32 notmuch@notmuchmail.org
\r
33 Subject: Re: [PATCH 3/4] emacs: Add pseudo saved search to match mail that no
\r
34 saved search matches
\r
35 In-Reply-To: <87liwkxxfm.fsf@servo.factory.finestructure.net>
\r
36 References: <cover.1309244829.git.jani@nikula.org>
\r
37 <e599ef4e125ba9410bb7fefe3208a39079ba8383.1309244829.git.jani@nikula.org>
\r
38 <87liwkxxfm.fsf@servo.factory.finestructure.net>
\r
39 User-Agent: Notmuch/0.5-232-g917e874 (http://notmuchmail.org) Emacs/23.1.1
\r
41 Date: Wed, 29 Jun 2011 20:15:22 +0000
\r
42 Message-ID: <87y60kv1gl.fsf@nikula.org>
\r
44 Content-Type: text/plain; charset=us-ascii
\r
45 X-BeenThere: notmuch@notmuchmail.org
\r
46 X-Mailman-Version: 2.1.13
\r
48 List-Id: "Use and development of the notmuch mail system."
\r
49 <notmuch.notmuchmail.org>
\r
50 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
51 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
52 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
53 List-Post: <mailto:notmuch@notmuchmail.org>
\r
54 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
55 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
56 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
57 X-List-Received-Date: Wed, 29 Jun 2011 20:15:30 -0000
\r
59 On Wed, 29 Jun 2011 12:14:05 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
\r
60 Non-text part: multipart/signed
\r
61 > On Tue, 28 Jun 2011 07:31:31 +0000, Jani Nikula <jani@nikula.org> wrote:
\r
62 > > Add a pseudo saved search that matches all the mail that no other saved
\r
63 > > search matches. Add new customization option notmuch-saved-searches-nomatch
\r
64 > > to enable and name the pseudo saved search.
\r
66 > Hi, Jani. I haven't looked too closely at these patches yet, although
\r
67 > they seem to look ok at first glance. However, I would like to argue
\r
68 > *against* using new customization variables for the names of certain
\r
69 > static saved searches. For instance I don't see the point of the
\r
70 > "notmuch-saved-searches-nomatch" and "notmuch-tags-nomatch"
\r
71 > customization variables. Do people *really* need to be able to
\r
72 > customize those names? Why not just pick a sensible name and go with
\r
75 Hi, I didn't add the customization specifically to customize the name,
\r
76 but rather to be able to switch the feature on/off. I felt that people
\r
77 might want to customize that. And while at it, customizing the name in
\r
78 the same variable seemed like a good idea. It's probably not desirable
\r
79 to collide with whatever search/tag names people might use.
\r
81 So to clarify, do you prefer having on/off switches, or just enabling
\r
82 this without customization at all? Personally I'd shy away from the
\r
83 latter, but I guess it depends on how useful vs. distracting people find
\r
86 > Customization is great, but if there's too much the code and
\r
87 > customization UI become overly cluttered and hard to parse.
\r