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