Re: [PATCH 2/3] show: output Reply-To headers
authorAustin Clements <amdragon@MIT.EDU>
Thu, 5 Jul 2012 15:18:21 +0000 (11:18 +2000)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:48:00 +0000 (09:48 -0800)
06/bba3d8771208daa63d6aeec43cf75cd7108cf7 [new file with mode: 0644]

diff --git a/06/bba3d8771208daa63d6aeec43cf75cd7108cf7 b/06/bba3d8771208daa63d6aeec43cf75cd7108cf7
new file mode 100644 (file)
index 0000000..1520569
--- /dev/null
@@ -0,0 +1,135 @@
+Return-Path: <amdragon@mit.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 8C27B431FAF\r
+       for <notmuch@notmuchmail.org>; Thu,  5 Jul 2012 08:18:26 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id Y1bLOMDW8Jid for <notmuch@notmuchmail.org>;\r
+       Thu,  5 Jul 2012 08:18:26 -0700 (PDT)\r
+Received: from dmz-mailsec-scanner-2.mit.edu (DMZ-MAILSEC-SCANNER-2.MIT.EDU\r
+       [18.9.25.13])\r
+       by olra.theworths.org (Postfix) with ESMTP id DEC08431FAE\r
+       for <notmuch@notmuchmail.org>; Thu,  5 Jul 2012 08:18:25 -0700 (PDT)\r
+X-AuditID: 1209190d-b7fd56d000000933-20-4ff5b03f613f\r
+Received: from mailhub-auth-3.mit.edu ( [18.9.21.43])\r
+       by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP\r
+       id 73.C1.02355.F30B5FF4; Thu,  5 Jul 2012 11:18:23 -0400 (EDT)\r
+Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])\r
+       by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id q65FIMRd030477; \r
+       Thu, 5 Jul 2012 11:18:23 -0400\r
+Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91])\r
+       (authenticated bits=0)\r
+       (User authenticated as amdragon@ATHENA.MIT.EDU)\r
+       by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q65FILNf007444\r
+       (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT);\r
+       Thu, 5 Jul 2012 11:18:22 -0400 (EDT)\r
+Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77)\r
+       (envelope-from <amdragon@mit.edu>)\r
+       id 1Smnoz-0003df-BI; Thu, 05 Jul 2012 11:18:21 -0400\r
+Date: Thu, 5 Jul 2012 11:18:21 -0400\r
+From: Austin Clements <amdragon@MIT.EDU>\r
+To: Mark Walters <markwalters1009@gmail.com>\r
+Subject: Re: [PATCH 2/3] show: output Reply-To headers\r
+Message-ID: <20120705151821.GF21653@mit.edu>\r
+References: <1340508470-16606-1-git-send-email-novalazy@gmail.com>\r
+       <1340508470-16606-2-git-send-email-novalazy@gmail.com>\r
+       <87vci471tw.fsf@servo.finestructure.net>\r
+       <20120704115951.GC2342@hili.localdomain>\r
+       <87pq8c6zad.fsf@servo.finestructure.net>\r
+       <20120704182459.GI2342@hili.localdomain>\r
+       <87vci2egr4.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Content-Disposition: inline\r
+In-Reply-To: <87vci2egr4.fsf@qmul.ac.uk>\r
+User-Agent: Mutt/1.5.21 (2010-09-15)\r
+X-Brightmail-Tracker:\r
+ H4sIAAAAAAAAA+NgFprNKsWRmVeSWpSXmKPExsUixCmqrWu/4au/QfchQ4s9+7wsVs/lsbh+\r
+       cyazxfPWvUwOLB53T3N57Jx1l93j2apbzAHMUVw2Kak5mWWpRfp2CVwZV7dnFuwVqbg0pZG5\r
+       gXGBQBcjJ4eEgIlE/6wpTBC2mMSFe+vZuhi5OIQE9jFKHF1+kBkkISSwnlHi9eMEiMQJJolj\r
+       Nx+yQDhLGCU6D9xiA6liEVCRWLK5AayDTUBDYtv+5YwgtoiAjsTtQwvYQRqYBZoYJVZsPsgC\r
+       khAWMJO4OruNFcTmBSr63nmXCWLqUSaJhe/XMEIkBCVOznwC1sAsoCVx499LoCIOIFtaYvk/\r
+       DhCTE2jZi7miIBWiQDdMObmNbQKj0CwkzbOQNM9CaF7AyLyKUTYlt0o3NzEzpzg1Wbc4OTEv\r
+       L7VI10gvN7NELzWldBMjONwleXcwvjuodIhRgINRiYfXKPeLvxBrYllxZe4hRkkOJiVR3k3r\r
+       vvoL8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuHtzQDK8aYkVlalFuXDpKQ5WJTEea+k3PQXEkhP\r
+       LEnNTk0tSC2CycpwcChJ8G5fD9QoWJSanlqRlplTgpBm4uAEGc4DNLwJpIa3uCAxtzgzHSJ/\r
+       ilGXY92bIzcYhVjy8vNSpcR520GKBECKMkrz4ObA0tQrRnGgt4R5m0GqeIApDm7SK6AlTEBL\r
+       8hZ/AllSkoiQkmpgtPkfv709oGJfwjzOpt5JvVwRxnZOF56tC972gUMpxtGn/+nTKcYLrqp7\r
+       LT84k6XN101xx/988ZlHO1ha7HuMN7z7n3ZbY5rqxY9x9Tv2p0fuf8rklGN3T6ak7VGA1bJV\r
+       /curjVjNuTW2ZrFcX+bwLPjVrYDs2fds5wo6xfVedVnkuSxmikq3EktxRqKhFnNRcSIAMMI2\r
+       Yy4DAAA=\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Thu, 05 Jul 2012 15:18:26 -0000\r
+\r
+Quoth Mark Walters on Jul 05 at  9:47 am:\r
+> On Wed, 04 Jul 2012, Peter Wang <novalazy@gmail.com> wrote:\r
+> > On Tue, 03 Jul 2012 19:22:18 -0700, Jameson Graef Rollins <jrollins@finestructure.net> wrote:\r
+> >> On Tue, Jul 03 2012, Peter Wang <novalazy@gmail.com> wrote:\r
+> >> > I want to see what the sender intended, before hitting reply.\r
+> >> \r
+> >> Given that there have been requests to see a lot of other headers as\r
+> >> well, we probably need to have a discussion about which ones are worth\r
+> >> of emitting, and how we give the user some more general control to see\r
+> >> the ones they want.  Either that or we just emit them all?\r
+> >\r
+> > If we start with the obvious:\r
+> >\r
+> >   notmuch show --output-headers=date,from,subject,to,cc,reply-to ...\r
+> >\r
+> > with the default being the current set.\r
+> >\r
+> > Emitting everything would be easier but seems wasteful.  I just looked\r
+> > at a random message: in RFC822 syntax the header is 4073 bytes, and the\r
+> > body is 1116 bytes.  Keeping only the fields that notmuch emits reduces\r
+> > the header to 295 bytes.  Reply-To is 92 bytes, but not every message\r
+> > has that.\r
+> \r
+> I wonder if it would make sense for this option to be combined with\r
+> something like\r
+> id:"1341041595-5858-1-git-send-email-markwalters1009@gmail.com" which\r
+> chooses whether to output the body of the message or not.\r
+> \r
+> Maybe something like --output=short|medium|full\r
+> with short being just the brief headers, medium being the current\r
+> default of brief headers and text bodies, and full being message with\r
+> all headers.\r
+> \r
+> I am not sure I like it (as someone will want full headers and no\r
+> bodies!) but we don't want the command line to get too cluttered.\r
+\r
+This option seems like the type of thing that would be used primarily\r
+by frontends, so it matters much more that they have control over the\r
+output than that the command line is terse.  We should provide\r
+reasonable defaults for the occasional flesh and blood call to the\r
+CLI, but I don't think we need to cater to that use.\r
+\r
+> Another possibility for this particular choice: could a list of wanted\r
+> headers be included in the config file? Since I think you want it for\r
+> "user wants to see it" reasons rather than "program needs it to do\r
+> something" reasons that might make sense.\r
+\r
+This would make a lot of sense in the frontend configuration (so much\r
+so that we already have it!  But it's currently limited to removing\r
+headers).  Also, if it's in the notmuch configuration, then when\r
+programs do need the headers to do something, it becomes very\r
+difficult to request what they need.\r