Re: [PATCH 0/4] Allow specifying alternate names for addresses in other_email
[notmuch-archives.git] / 4e / 5f31b16d9d6a0e1c497c6a89b6da8464646ffa
1 Return-Path: <amdragon@mit.edu>\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 E3545429E25\r
6         for <notmuch@notmuchmail.org>; Tue, 10 Jan 2012 08:05:00 -0800 (PST)\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: -0.7\r
10 X-Spam-Level: \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 ttbvYZ12pWj2 for <notmuch@notmuchmail.org>;\r
16         Tue, 10 Jan 2012 08:05:00 -0800 (PST)\r
17 Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU\r
18         [18.7.68.37])\r
19         by olra.theworths.org (Postfix) with ESMTP id 612F7431FB6\r
20         for <notmuch@notmuchmail.org>; Tue, 10 Jan 2012 08:05:00 -0800 (PST)\r
21 X-AuditID: 12074425-b7f4a6d0000008e0-ad-4f0c61abf56f\r
22 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35])\r
23         by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP\r
24         id 3B.3B.02272.BA16C0F4; Tue, 10 Jan 2012 11:04:59 -0500 (EST)\r
25 Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
26         by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id q0AG4sg5000391; \r
27         Tue, 10 Jan 2012 11:04:54 -0500\r
28 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
29         (authenticated bits=0)\r
30         (User authenticated as amdragon@ATHENA.MIT.EDU)\r
31         by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q0AG4rkx005292\r
32         (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
33         Tue, 10 Jan 2012 11:04:53 -0500 (EST)\r
34 Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
35         (envelope-from <amdragon@mit.edu>)\r
36         id 1RkeC6-0001w6-K8; Tue, 10 Jan 2012 11:05:02 -0500\r
37 Date: Tue, 10 Jan 2012 11:05:02 -0500\r
38 From: Austin Clements <amdragon@MIT.EDU>\r
39 To: David Edmondson <dme@dme.org>\r
40 Subject: Re: [PATCH] emacs: Improve `notmuch-hello' display on ttys.\r
41 Message-ID: <20120110160502.GN20796@mit.edu>\r
42 References: <1326190528-3548-1-git-send-email-dme@dme.org>\r
43         <20120110153650.GM20796@mit.edu>\r
44         <cunlipfo8yp.fsf@hotblack-desiato.hh.sledj.net>\r
45 MIME-Version: 1.0\r
46 Content-Type: text/plain; charset=us-ascii\r
47 Content-Disposition: inline\r
48 In-Reply-To: <cunlipfo8yp.fsf@hotblack-desiato.hh.sledj.net>\r
49 User-Agent: Mutt/1.5.21 (2010-09-15)\r
50 X-Brightmail-Tracker:\r
51  H4sIAAAAAAAAA+NgFprIKsWRmVeSWpSXmKPExsUixCmqrLs6kcffYN87K4t9d7YwWVy/OZPZ\r
52         gclj1/O/TB7PVt1iDmCK4rJJSc3JLEst0rdL4Mo4fm4iS8Emrop37b8ZGxhncHQxcnJICJhI\r
53         nD40jR3CFpO4cG89WxcjF4eQwD5Gie87ZkA5GxglFqxZywThnGSSOHjmDDuEs4RR4knPE2aQ\r
54         fhYBVYnlP04xgdhsAhoS2/YvZwSxRQQUJf5/WwG2g1lAWuLb72awGmEBF4lHB06wgti8AjoS\r
55         F7Z8YYQY2s8o8fLAI3aIhKDEyZlPWCCatSRu/HsJ1MwBNmj5P7AfOAVsJO6d28cGYosKqEhM\r
56         ObmNbQKj0Cwk3bOQdM9C6F7AyLyKUTYlt0o3NzEzpzg1Wbc4OTEvL7VI10IvN7NELzWldBMj\r
57         KLTZXVR3ME44pHSIUYCDUYmH96QGt78Qa2JZcWXuIUZJDiYlUd6LCTz+QnxJ+SmVGYnFGfFF\r
58         pTmpxYcYJTiYlUR4Wa2BcrwpiZVVqUX5MClpDhYlcV5NrXd+QgLpiSWp2ampBalFMFkZDg4l\r
59         Cd6nIEMFi1LTUyvSMnNKENJMHJwgw3mAhtslggwvLkjMLc5Mh8ifYtTluN449xyjEEtefl6q\r
60         lDivLEiRAEhRRmke3BxYSnrFKA70ljDv8VCgKh5gOoOb9ApoCRPQElFRbpAlJYkIKakGxpU3\r
61         18xVnJl0tc7aotp7yuGF3Q+4bfaETp7ac1yiaO7HOcGuaiXch14dqTboqLzh9Tw0u0Lc6IDG\r
62         gx1VXwVenOKepnzVtqViXZiH1xT5NSZap59qVJ9e1/DtNMM6Zz3ZQ41L0ncl8vWw2D+MeXZE\r
63         adqJuJzDd7IEEkqOH97x498F/ijFZtezjUosxRmJhlrMRcWJAJo4+T0kAwAA\r
64 Cc: notmuch@notmuchmail.org\r
65 X-BeenThere: notmuch@notmuchmail.org\r
66 X-Mailman-Version: 2.1.13\r
67 Precedence: list\r
68 List-Id: "Use and development of the notmuch mail system."\r
69         <notmuch.notmuchmail.org>\r
70 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
71         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
72 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
73 List-Post: <mailto:notmuch@notmuchmail.org>\r
74 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
75 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
76         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
77 X-List-Received-Date: Tue, 10 Jan 2012 16:05:01 -0000\r
78 \r
79 Quoth David Edmondson on Jan 10 at  3:47 pm:\r
80 > On Tue, 10 Jan 2012 10:36:50 -0500, Austin Clements <amdragon@MIT.EDU> wrote:\r
81 > > LGTM, though would it be easier to put this in the else clause of the\r
82 > > if after the setq count?\r
83\r
84 > Agreed. I got confused thinking about it due to the empty elements in\r
85 > the matrix, but perhaps that doesn't matter. I'll continue to think, but\r
86 > would rather not delay fixing the bug.\r
87 \r
88 Fair enough.\r
89 \r
90 > > Is it possible for a tag in the last column to be just long enough to\r
91 > > make the line still wrap?  Somehow my current tag set doesn't trigger\r
92 > > this bug, so I can't test this case (and I admit I can't follow\r
93 > > notmuch-hello-insert-tags well enough to reason this out).\r
94\r
95 > With a sufficiently narrow window it's always possible to generate wrap,\r
96 > of course. I couldn't make it happen for any window width that seemed\r
97 > reasonable.\r
98 \r
99 I should have specified more than one column.  Clearly if you're down\r
100 to one column it's always possible to wrap, but if you have more than\r
101 one, does the code always reduce the number of columns in preference\r
102 to allowing a particularly long tag name to wrap a line?  Based on\r
103 your testing, it sounds like it handles this correctly.  (Even if it\r
104 didn't, this shouldn't block this patch; it's related, but not the\r
105 same issue.)\r