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 1F334431FB6
\r
6 for <notmuch@notmuchmail.org>; Sat, 5 May 2012 04:57:43 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.321 tagged_above=-999 required=5
\r
12 tests=[NO_DNS_FOR_FROM=0.379, 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 3O9tiB1dPfbH for <notmuch@notmuchmail.org>;
\r
17 Sat, 5 May 2012 04:57:36 -0700 (PDT)
\r
18 Received: from mail-lpp01m010-f53.google.com (mail-lpp01m010-f53.google.com
\r
19 [209.85.215.53]) (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 424F3431FAE
\r
22 for <notmuch@notmuchmail.org>; Sat, 5 May 2012 04:57:36 -0700 (PDT)
\r
23 Received: by lahc1 with SMTP id c1so2834909lah.26
\r
24 for <notmuch@notmuchmail.org>; Sat, 05 May 2012 04:57:34 -0700 (PDT)
\r
25 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
26 d=google.com; s=20120113;
\r
27 h=from:to:cc:subject:in-reply-to:references:user-agent:date
\r
28 :message-id:mime-version:content-type:x-gm-message-state;
\r
29 bh=LGFyqXiZbVQ094o5PZVrwNi4GejyuF9VCfi0AIZO690=;
\r
30 b=ck6iu1lxSL/W7SYRpz1/ezBJ1hGmzeM1S1JpCA4lIj+A20EfKbtUhrc2x9OD8FckMu
\r
31 ttMlm1MabXBuomRUvC4r+ypXsSmfrE/Zw4zhy5qTRxdh5vQM18guWYURO63xKmMNesxV
\r
32 a1fySgaGypEzzhCcq1Bf3ZLMpQTdN9PYBOe2ebnIa8wW/uEoonp8oUNZtpE7/DZ6h+T4
\r
33 0hQ3VPDYGIspKVFt/5+Fa3yTeAff7x1XyVDNPBwdOUl8jodoh+o4PcSu1j3334IRZ6fb
\r
34 ToBEYEqGoWeA6NjRfNRN3DsO6sFkR99d9n8MTag9Lv2sOoF1Ea40gRork8IxI4tlPAfT
\r
36 Received: by 10.112.102.136 with SMTP id fo8mr4406388lbb.106.1336219054645;
\r
37 Sat, 05 May 2012 04:57:34 -0700 (PDT)
\r
38 Received: from localhost (dsl-hkibrasgw4-fe50dc00-68.dhcp.inet.fi.
\r
40 by mx.google.com with ESMTPS id fx5sm14881446lbb.5.2012.05.05.04.57.31
\r
41 (version=SSLv3 cipher=OTHER); Sat, 05 May 2012 04:57:33 -0700 (PDT)
\r
42 From: Jani Nikula <jani@nikula.org>
\r
43 To: Mark Walters <markwalters1009@gmail.com>,
\r
44 Jameson Graef Rollins <jrollins@finestructure.net>,
\r
45 Austin Clements <amdragon@MIT.EDU>
\r
46 Subject: Re: [Patch v2 0/3] emacs: allow show to colour based on tags and
\r
48 In-Reply-To: <87txzw1otb.fsf@qmul.ac.uk>
\r
49 References: <1335739697-8501-1-git-send-email-markwalters1009@gmail.com>
\r
50 <20120429230220.GO2704@mit.edu>
\r
51 <87397jwhjp.fsf@servo.finestructure.net>
\r
52 <87txzw1otb.fsf@qmul.ac.uk>
\r
53 User-Agent: Notmuch/0.12+169~g45438b0 (http://notmuchmail.org) Emacs/23.3.1
\r
55 Date: Sat, 05 May 2012 14:57:29 +0300
\r
56 Message-ID: <878vh6j0wm.fsf@nikula.org>
\r
58 Content-Type: text/plain; charset=us-ascii
\r
60 ALoCoQl7dPlJ5VrphF+KYZONHGQ55lsUFg+e6RnoaXG528amo+WTxbaPUgTuoaZ7hHklFt4jVLgu
\r
61 Cc: notmuch@notmuchmail.org
\r
62 X-BeenThere: notmuch@notmuchmail.org
\r
63 X-Mailman-Version: 2.1.13
\r
65 List-Id: "Use and development of the notmuch mail system."
\r
66 <notmuch.notmuchmail.org>
\r
67 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
68 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
69 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
70 List-Post: <mailto:notmuch@notmuchmail.org>
\r
71 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
72 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
73 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
74 X-List-Received-Date: Sat, 05 May 2012 11:57:43 -0000
\r
76 On Fri, 04 May 2012, Mark Walters <markwalters1009@gmail.com> wrote:
\r
77 > On Wed, 02 May 2012, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
\r
78 >> On Sun, Apr 29 2012, Austin Clements <amdragon@MIT.EDU> wrote:
\r
79 >>> I haven't really looked at this series yet, but I do have a quick
\r
80 >>> high-level question. Why use separate customization variables for the
\r
81 >>> colors in search and show mode? Wouldn't it make more sense to set
\r
82 >>> the colors just once and use them in both modes?
\r
84 >> I thought about this myself as soon as I read the patch. I think I
\r
85 >> would always want the colors to match, so it would make sense to me to
\r
86 >> set them in one place.
\r
90 > I think both are useful (see my reply to Austin) but having show apply
\r
91 > the faces from notmuch-search first seems a good idea.
\r
93 > There are a couple of extra reasons why I like the show ones
\r
94 > separate. One is that I like to colour headerlines of matching messages to
\r
95 > highlight them, but in search mode that would highlight every
\r
96 > line. Secondly, I colour some things "negatively" in show mode: for
\r
97 > example I show excluded messages in grey. This negative colouring does
\r
98 > not make sense for search mode because I would only want to grey out
\r
99 > results where all messages were excluded not results where at least one
\r
100 > message is excluded. Of course we don't show entirely excluded threads
\r
101 > in search, but similar comments apply to say the "replied" tag: I could
\r
102 > show those in green (on the basis they are "dealt with") but I would not
\r
103 > want a thread coloured green just because I have replied to one message
\r
106 I completely agree with having separate faces for search and show.
\r
108 >>> BTW, I like how this clearly distinguishes tags and flags. I wonder
\r
109 >>> if we could transition to flags for some information that's current
\r
110 >>> shoe-horned into tags but actually represents immutable information
\r
111 >>> about a message (attachment, signed, and encrypted or so).
\r
113 >> Yes! As Austin probably remembers, we've discussed this before. I
\r
114 >> definitely agree that it makes sense to somehow distinguish "immutable"
\r
115 >> information that is a fundamental, unchanging/able property of the
\r
116 >> message, and it might be nice to look ahead to that here.
\r
118 > In essence I agree: my only concern is can the user search for these
\r
119 > immutable things, and what syntax is used there.
\r
121 Making a separation between immutable properties (like "attachment" or
\r
122 "signed") and tags is a good goal, but AFAICS doing that right requires
\r
123 changes all the way down to the library. I wouldn't worry about it at
\r
124 all here. From emacs UI perspective they're all just tags. This is here
\r
125 now, and works; there's no need to complicate matters when there's
\r
126 nobody doing anything about the plumbing. Fixing this later is a trivial
\r
127 matter compared to the plumbing work in cli and lib.
\r
139 > _______________________________________________
\r
140 > notmuch mailing list
\r
141 > notmuch@notmuchmail.org
\r
142 > http://notmuchmail.org/mailman/listinfo/notmuch
\r