1 Return-Path: <tomi.ollila@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 836B1431FDB
\r
6 for <notmuch@notmuchmail.org>; Fri, 9 Jan 2015 06:13:31 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=2.438 tagged_above=-999 required=5
\r
12 tests=[DNS_FROM_AHBL_RHSBL=2.438] 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 sUQHJeuBrShs for <notmuch@notmuchmail.org>;
\r
16 Fri, 9 Jan 2015 06:13:27 -0800 (PST)
\r
17 Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 7F57B431FD8
\r
19 for <notmuch@notmuchmail.org>; Fri, 9 Jan 2015 06:13:27 -0800 (PST)
\r
20 Received: from guru.guru-group.fi (localhost [IPv6:::1])
\r
21 by guru.guru-group.fi (Postfix) with ESMTP id 3B405100090;
\r
22 Fri, 9 Jan 2015 16:13:00 +0200 (EET)
\r
23 From: Tomi Ollila <tomi.ollila@iki.fi>
\r
24 To: Michal Sojka <sojkam1@fel.cvut.cz>, David Bremner <david@tethera.net>,
\r
25 notmuch@notmuchmail.org
\r
26 Subject: Re: [PATCH v3 10/10] cli: address: Add --filter-by
\r
27 option to configure address filtering
\r
28 In-Reply-To: <87egr46qcs.fsf@steelpick.2x.cz>
\r
29 References: <1415147159-19946-1-git-send-email-sojkam1@fel.cvut.cz>
\r
30 <1415147159-19946-11-git-send-email-sojkam1@fel.cvut.cz>
\r
31 <87vbkrfs66.fsf@maritornes.cs.unb.ca>
\r
32 <m2d26yhfmk.fsf@guru.guru-group.fi>
\r
33 <87egr46qcs.fsf@steelpick.2x.cz>
\r
34 User-Agent: Notmuch/0.19+14~ge04617b (http://notmuchmail.org) Emacs/24.3.1
\r
35 (x86_64-unknown-linux-gnu)
\r
36 X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
\r
37 $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
\r
38 !)g;OY^,BjTbr)Np:%c_o'jj,Z
\r
39 Date: Fri, 09 Jan 2015 16:13:00 +0200
\r
40 Message-ID: <m2h9w0ujo3.fsf@guru.guru-group.fi>
\r
42 Content-Type: text/plain
\r
43 X-BeenThere: notmuch@notmuchmail.org
\r
44 X-Mailman-Version: 2.1.13
\r
46 List-Id: "Use and development of the notmuch mail system."
\r
47 <notmuch.notmuchmail.org>
\r
48 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
50 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
51 List-Post: <mailto:notmuch@notmuchmail.org>
\r
52 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
53 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
54 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
55 X-List-Received-Date: Fri, 09 Jan 2015 14:13:31 -0000
\r
57 On Fri, Jan 09 2015, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
\r
61 > sorry for longer response time :)
\r
63 > On Thu, Jan 01 2015, Tomi Ollila wrote:
\r
64 >> On Wed, Dec 31 2014, David Bremner <david@tethera.net> wrote:
\r
66 >>> Michal Sojka <sojkam1@fel.cvut.cz> writes:
\r
68 >>>> This option allows to configure the criterion for duplicate address
\r
69 >>>> filtering. Without this option, all unique combinations of name and
\r
70 >>>> address parts are printed. This option allows to filter the output
\r
71 >>>> more, for example to only contain unique address parts.
\r
73 >>> I had the feeling there was some "controversy" about the UI here, but
\r
74 >>> following back the 3 versions of the series I didn't see it. Does that
\r
75 >>> mean we just need to sanity check the code, or are there outstanding
\r
78 > I'd tend to rename this option to --unique as it was in some previous
\r
79 > version of the patch. Another thing in my mind is the implementation of
\r
80 > the --complete option mentioned in id:878uid9qjl.fsf@nautilus.nautilus.
\r
81 > This would also involve some kind of address filtering. I'll look into
\r
82 > this and send patches later.
\r
84 >> I have intentionally been guiet on this during the review process of the
\r
85 >> other patches to not slow down the acceptance of the others. I have not
\r
86 >> got enough time to look the implemenentation or think this last patch
\r
87 >> further -- from the user interface point of view I recall seeing there
\r
88 >> both useless features (but which might be warranted by implementation
\r
89 >> simplicity) and missing features (but which might not be there due to
\r
90 >> difficulty in implementation). Also, I am not sure whether the --filter-by
\r
91 >> is good option (and options descriptive...)...
\r
93 > I'd be interested in what are these "missing features".
\r
95 Last night when I tried to catch sleep I was also thinking of this...
\r
96 ... let's see what I remember...
\r
98 First, Currently if we have addresses:
\r
100 "Uni Que" <unique@example.org>
\r
101 "Uni Que" <Unique@Example.Org>
\r
103 I presume these are thought as a separate addresses -- and an option to
\r
104 thought these as the same would be useful.
\r
106 but let's consider second set of addresses:
\r
108 "Uni Que" <unique@example.org>
\r
109 "Uni Keko" <unique@example.org>
\r
111 Now, if there were an option to consider these 2 as the same, that would
\r
112 hide user from one of the names -- It is clear that "Uni Que" is the right
\r
113 one but if only "Uni Keko" (sleepyhead, that is) is shown user don't have
\r
114 a choice to select the right one. I am not sure what the use case for
\r
115 "uniquing" these 2 were.
\r
117 Finally (for now), 3rd set of addresses
\r
119 "Uni Que" <unique@example.org>
\r
120 "Uni Que" <unique@foobar.invalid>
\r
122 Now, if there were an option to consider these 2 as same, and
\r
123 user is then given "Uni Que" <unique@foobar.invalid> (which clearly is
\r
124 the wrong one) I don't see the usefullness of this option...
\r
126 IMO I don't see a case having such an options there, but these are my
\r
127 opinions, feel free to bikes^H^H^H^H^H discuss further :D
\r
131 PS: The "missing features" not thought now -- the only one I can quickly
\r
132 remember is uniq(1) style option -- uniq consecutive addresses to one --
\r
133 to do this we'd first need the no-unique-at-all option... and of course
\r
134 I have a use case for this :D
\r
155 > _______________________________________________
\r
156 > notmuch mailing list
\r
157 > notmuch@notmuchmail.org
\r
158 > http://notmuchmail.org/mailman/listinfo/notmuch
\r