Re: [PATCH] emacs: wash: make word-wrap bound message width
[notmuch-archives.git] / 2c / 321c2e42e72bf4d12ac46ada76625220dd216c
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 6FC50431FC4\r
6         for <notmuch@notmuchmail.org>; Tue, 25 Sep 2012 12:31:42 -0700 (PDT)\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 Ubto8pQMBQSC for <notmuch@notmuchmail.org>;\r
16         Tue, 25 Sep 2012 12:31:42 -0700 (PDT)\r
17 Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU\r
18         [18.7.68.36])\r
19         by olra.theworths.org (Postfix) with ESMTP id D7729431FAF\r
20         for <notmuch@notmuchmail.org>; Tue, 25 Sep 2012 12:31:41 -0700 (PDT)\r
21 X-AuditID: 12074424-b7fce6d000000925-dd-5062069d9b98\r
22 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39])\r
23         by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP\r
24         id A5.4E.02341.D9602605; Tue, 25 Sep 2012 15:31:41 -0400 (EDT)\r
25 Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
26         by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id q8PJVefs020143; \r
27         Tue, 25 Sep 2012 15:31:40 -0400\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 q8PJVbDu001553\r
32         (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
33         Tue, 25 Sep 2012 15:31:39 -0400 (EDT)\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 1TGar3-0008Nw-An; Tue, 25 Sep 2012 15:31:37 -0400\r
37 Date: Tue, 25 Sep 2012 15:31:37 -0400\r
38 From: Austin Clements <amdragon@MIT.EDU>\r
39 To: Olivier Berger <olivier.berger@it-sudparis.eu>\r
40 Subject: Re: Provide an option to make thread summaries keep initial subject\r
41 Message-ID: <20120925193137.GM26662@mit.edu>\r
42 References: <87zk4eqech.fsf@inf-8657.int-evry.fr>\r
43 MIME-Version: 1.0\r
44 Content-Type: text/plain; charset=us-ascii\r
45 Content-Disposition: inline\r
46 In-Reply-To: <87zk4eqech.fsf@inf-8657.int-evry.fr>\r
47 User-Agent: Mutt/1.5.21 (2010-09-15)\r
48 X-Brightmail-Tracker:\r
49  H4sIAAAAAAAAA+NgFmpileLIzCtJLcpLzFFi42IRYrdT153LlhRgcPqPuMX1mzOZLRrPtLM5\r
50         MHk8advE4vFs1S3mAKYoLpuU1JzMstQifbsEroz3TR0sBQt5K+bNPsDSwHiXq4uRk0NCwETi\r
51         9NfrTBC2mMSFe+vZuhi5OIQE9jFKXF/3hhXC2cAo8WDLMyjnJJPEuX9roMqWMEpMOLeBBaSf\r
52         RUBV4uylmewgNpuAhsS2/csZQWwRASOJbc1bWUFsZgFpiW+/m8H2CQv4SBx5tIIZxOYV0JH4\r
53         t2M6kM0BNNRQ4thCHoiwoMTJmU9YIFq1JG78e8kEUgIyZvk/DhCTE2j6hFecIBWiAioSU05u\r
54         Y5vAKDQLSfMsJM2zEJoXMDKvYpRNya3SzU3MzClOTdYtTk7My0st0jXXy80s0UtNKd3ECA5q\r
55         F5UdjM2HlA4xCnAwKvHwHnieGCDEmlhWXJl7iFGSg0lJlPfFP6AQX1J+SmVGYnFGfFFpTmrx\r
56         IUYJDmYlEV5jkHLelMTKqtSifJiUNAeLkjjv9ZSb/kIC6YklqdmpqQWpRTBZGQ4OJQneA6xJ\r
57         AUKCRanpqRVpmTklCGkmDk6Q4TxAwwtAaniLCxJzizPTIfKnGBWlxHn7QRICIImM0jy4XljS\r
58         ecUoDvSKMO8mkCoeYMKC634FNJgJaDD/njiQwSWJCCmpBsbMN6YKph+m1Pm9OscxPWVLJbNJ\r
59         qv0z10Wz3yhxtG5nuX16mQZ3afc9sxgD4yL9q18d77c/98m/kuISo/3mWcr/zrVN7vecjU/2\r
60         9t7VbJ+2z+3/XctXCocNPjRGzA3pOMVuJqK7MM60VvdvaoPcA4OHS7aVfnaOf535aMO1CXfu\r
61         2C341bm866QSS3FGoqEWc1FxIgDUgfb2FQMAAA==\r
62 Cc: notmuch@notmuchmail.org\r
63 X-BeenThere: notmuch@notmuchmail.org\r
64 X-Mailman-Version: 2.1.13\r
65 Precedence: list\r
66 List-Id: "Use and development of the notmuch mail system."\r
67         <notmuch.notmuchmail.org>\r
68 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
69         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
70 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
71 List-Post: <mailto:notmuch@notmuchmail.org>\r
72 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
73 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
74         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
75 X-List-Received-Date: Tue, 25 Sep 2012 19:31:42 -0000\r
76 \r
77 Quoth Olivier Berger on Sep 25 at  6:03 pm:\r
78 > Hi.\r
79\r
80 > Whenever a participant changes the subject in the middle of a thread,\r
81 > the summary reported by notmuch search will change.\r
82\r
83 > However, the result is that some mails tend to "disappear" from search\r
84 > results, when (bad) participants reply instead of composing a new mail,\r
85 > and change a subject (see\r
86 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688699 for more details\r
87 > on that problem, and a discussion). Of course, they're still there, but\r
88 > their subject being masked, one may then grep or C-s for a particular\r
89 > subject and miss them.\r
90\r
91 > I think it would be interesting to allow notmuch to potentially keep the\r
92 > original subject and not the most recent one for the thread summaries.\r
93\r
94 > What do you think ?\r
95 \r
96 I think this would be fantastic.  I've proposed unconditionally\r
97 showing the earliest subject before and it seems that people who\r
98 correspond mostly with those who have good threading etiquette would\r
99 prefer this change, but those who correspond with more people who use\r
100 'reply' like an address book prefer the current behavior.\r
101 \r
102 Another option, which I'd like to experiment with but haven't found\r
103 the time, is to show *all* distinct subjects for matched messages in a\r
104 thread (modulo "Re:", etc) in the summary buffer, probably on multiple\r
105 lines.  Since most threads only have a single unique subject, they\r
106 would appear just as they do now, but it would be clear when someone\r
107 (or something, like git) changed the subject mid-thread.  This\r
108 approach would be far more robust while retaining good usability, but\r
109 it would require more code than just changing our subject-picking\r
110 heuristic.\r