f7/2008ad73ef085ec3bf1caf2453270dd8df0d26

   1 Return-Path: <wking@tremily.us>\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 1F1A0431FBD\r
   6         for <notmuch@notmuchmail.org>; Sat,  8 Feb 2014 08:59:44 -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.1\r
  10 X-Spam-Level: \r
  11 X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5\r
  12         tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
  13         RCVD_IN_DNSWL_NONE=-0.0001] autolearn=disabled\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 bB8LMPfU6YzM for <notmuch@notmuchmail.org>;\r
  17         Sat,  8 Feb 2014 08:59:36 -0800 (PST)\r
  18 Received: from qmta06.westchester.pa.mail.comcast.net\r
  19         (qmta06.westchester.pa.mail.comcast.net [76.96.62.56])\r
  20         by olra.theworths.org (Postfix) with ESMTP id 4CF01431FBC\r
  21         for <notmuch@notmuchmail.org>; Sat,  8 Feb 2014 08:59:36 -0800 (PST)\r
  22 Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88])\r
  23         by qmta06.westchester.pa.mail.comcast.net with comcast\r
  24         id Ps4r1n0021uE5Es56szZjE; Sat, 08 Feb 2014 16:59:33 +0000\r
  25 Received: from odin.tremily.us ([24.18.63.50])\r
  26         by omta16.westchester.pa.mail.comcast.net with comcast\r
  27         id PszY1n00V152l3L3cszZvY; Sat, 08 Feb 2014 16:59:33 +0000\r
  28 Received: by odin.tremily.us (Postfix, from userid 1000)\r
  29         id 5E3D4FFFAFD; Sat,  8 Feb 2014 08:59:31 -0800 (PST)\r
  30 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tremily.us; s=odin;\r
  31         t=1391878771; bh=8QcRvo5qxr89BwLMrM1MtjBg/euDdILlEGHyekM4e0A=;\r
  32         h=Date:From:To:Cc:Subject:References:In-Reply-To;\r
  33         b=qLY70TJrynVvxe3cOQAccf98XQUpRz4owwEUCykMqGoeON7BwfdE61qqoo3uLazLh\r
  34         hV1h+0fgBjsHEqQRaY04ZFODdZe3WAB/ZKLNWgkwtp0pmJiJkQvDYn4Qw2lTaw6kOw\r
  35         6sGaS2quYiQswB6lyF06rfpJDQNHkUuEK5UQy4VM=\r
  36 Date: Sat, 8 Feb 2014 08:59:31 -0800\r
  37 From: "W. Trevor King" <wking@tremily.us>\r
  38 To: David Bremner <david@tethera.net>\r
  39 Subject: Re: [PATCH 2/2] emacs: Prefer Content-Description over filename for\r
  40         part buttons\r
  41 Message-ID: <20140208165931.GB17142@odin.tremily.us>\r
  42 References: <877g9chbay.fsf@qmul.ac.uk>\r
  43  <cover.1391423201.git.wking@tremily.us>\r
  44         <27be295875a7df782a83c9a2c09d06f9d321fe9e.1391423201.git.wking@tremily.us>\r
  45         <87vbwwosuw.fsf@qmul.ac.uk>     <20140203203418.GO14197@odin.tremily.us>\r
  46         <20140204013246.GQ19935@odin.tremily.us>        <87r47dojbt.fsf@zancas.localnet>\r
  47 MIME-Version: 1.0\r
  48 Content-Type: multipart/signed; micalg=pgp-sha1;\r
  49         protocol="application/pgp-signature"; boundary="wzJLGUyc3ArbnUjN"\r
  50 Content-Disposition: inline\r
  51 In-Reply-To: <87r47dojbt.fsf@zancas.localnet>\r
  52 OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8;\r
  53         url=http://tremily.us/pubkey.txt\r
  54 User-Agent: Mutt/1.5.22 (2013-10-16)\r
  55 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;\r
  56         s=q20121106; t=1391878773;\r
  57         bh=Z1rxuNTj0mhFz81iwB7rvoDg/D6jXbs4VcW/r3ssPWo=;\r
  58         h=Received:Received:Received:Date:From:To:Subject:Message-ID:\r
  59         MIME-Version:Content-Type;\r
  60         b=Q04aGfukgSYAnDwcrqn3pQhqxhbNULI2e/PaojIKaFLC8Wq1peBKcTxP7QXyBdhHt\r
  61         qzzp6LPuWaPgHX8lZipWXT7jBdRmuYDCvQCls3Jyxaj9Af4W/FsjuflxiO1eA1gm7f\r
  62         TfIxBiCCGQWiW11Cq5oIfmnTmj0nH7uHBuOjbWnd+cPYhPM8EBnwFkc+WRkaPbOTj/\r
  63         yABitZBZuoTqS52SzwPhOE/XsJQYiO6jFWqkaxz/EopCBfvssy+vx0kOV6oiNKwkwB\r
  64         nBWUCz2vsIfEODvk30Y+uvCtb/p7zOt9gmcAS5994VOfdPUnS3co+8ridouFPcwVBP\r
  65         Zg82kQY6/Lm1g==\r
  66 Cc: notmuch@notmuchmail.org\r
  67 X-BeenThere: notmuch@notmuchmail.org\r
  68 X-Mailman-Version: 2.1.13\r
  69 Precedence: list\r
  70 List-Id: "Use and development of the notmuch mail system."\r
  71         <notmuch.notmuchmail.org>\r
  72 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  73         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  74 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
  75 List-Post: <mailto:notmuch@notmuchmail.org>\r
  76 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  77 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  78         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  79 X-List-Received-Date: Sat, 08 Feb 2014 16:59:44 -0000\r
  80 \r
  81 \r
  82 --wzJLGUyc3ArbnUjN\r
  83 Content-Type: text/plain; charset=utf-8\r
  84 Content-Disposition: inline\r
  85 Content-Transfer-Encoding: quoted-printable\r
  86 \r
  87 On Sat, Feb 08, 2014 at 08:55:02AM -0400, David Bremner wrote:\r
  88 > "W. Trevor King" <wking@tremily.us> writes:\r
  89 > > Rather than patching this in Emacs, maybe we should collapse the\r
  90 > > =E2=80=9Cnot set=E2=80=9D and =E2=80=9Cset to empty string=E2=80=9D cas=\r
  91 es in notmuch-show.c?  I\r
  92 > > can't think of any reasons why someone would want to distinguish\r
  93 > > those two cases, and it's easier all around if we standardize the\r
  94 > > representation as far upstream as possible.\r
  95 >=20\r
  96 > Do the RFCs have anything to say about headers with empty content?\r
  97 > If not I'd be inclined to leave the CLI output as raw as possible,\r
  98 > just because people are always finding new ways to apply tools.\r
  99 \r
 100 RFC 2183 does not describe Content-Description, it just uses it in\r
 101 some examples [1].  In all the examples where Content-Description is\r
 102 present, the value is not empty.  RFC 2045 defines\r
 103 Content-Description, but it doesn't give all that much information\r
 104 [2]:\r
 105 \r
 106   The ability to associate some descriptive information with a given\r
 107   body is often desirable.  For example, it may be useful to mark an\r
 108   "image" body as "a picture of the Space Shuttle Endeavor."  Such\r
 109   text may be placed in the Content-Description header field.  This\r
 110   header field is always optional.\r
 111 \r
 112     description :=3D "Content-Description" ":" *text\r
 113 \r
 114   The description is presumed to be given in the US-ASCII character\r
 115   set, although the mechanism specified in RFC 2047 may be used for\r
 116   non-US-ASCII Content-Description values.\r
 117 \r
 118 I couldn't find more generic references to the meaning of empty header\r
 119 values, but I find it hard to imagine anyone assigning semantic value\r
 120 to an explicitly-empty description (vs. no Content-Description at\r
 121 all).\r
 122 \r
 123 Cheers,\r
 124 Trevor\r
 125 \r
 126 [1]: http://tools.ietf.org/html/rfc2183#section-3\r
 127 [2]: http://tools.ietf.org/html/rfc2045#section-8\r
 128 \r
 129 --=20\r
 130 This email may be signed or encrypted with GnuPG (http://www.gnupg.org).\r
 131 For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy\r
 132 \r
 133 --wzJLGUyc3ArbnUjN\r
 134 Content-Type: application/pgp-signature; name="signature.asc"\r
 135 Content-Description: OpenPGP digital signature\r
 136 \r
 137 -----BEGIN PGP SIGNATURE-----\r
 138 Version: GnuPG v2.0.22 (GNU/Linux)\r
 139 \r
 140 iQIcBAEBAgAGBQJS9mJxAAoJEKKfehoaNkbtlvUP/igWrkJJ1shtEUEExhVSzp+V\r
 141 BUGiAi3alGyx4ZFLcwAwF3L8kDBhoOkCX72CzGQMM8yG9TLqyqLuMHmBLmmn0O/n\r
 142 E25Q1zVQsBAQJ6loZGJ5NAdtjhknZtcU4HkB8ozLhpZZlhHKh4zNUcXU9R8pkruI\r
 143 0ngOzyYSRcEYEJilR47ooh/zvgc3y74gDSD0jZHfXYTjilEdPzXgbypbeVM8B1ZT\r
 144 nxMqrvuiDUIOxC8UFYiMhmOQtKHdOli7JQ935y5G1ODtx7yfpx6ub8plzVSJrZkv\r
 145 OQz1/raBzI6DuwuTnZ06ai3OQ2UXY3l8VcPs5u2uc6DItSwY566Zuwf4g4a9yT/K\r
 146 R2Vvt2XlmnfKzOQ+uSCu1Jg6QYbhD++PSvr5R6Tn6nVYUi9ogM8QAbq9FvpF1ROO\r
 147 A2HSqeg7CckX1Tr6TOzEun+BejRhEuK+njY4C4Tchjr0ixrj+/TTX4AyUoqwxRSP\r
 148 VfNI1E42VP5DS96Ng/SXU9L4VpFB042ItMVwPuyUyGgeX4WlYmimEmVMzzWjsdYg\r
 149 ltfZRP9z1grkVFxxSGs3Yj/aAHPcVENx3WSwGKx1h28hDvaPVB97kwA4QUqfzUyj\r
 150 DBXR3lRpuLNKPqaSq9gMc7yN8P8qA55uaUYzfJAk+xNbtfTbOm3QGAUksA8oC7cT\r
 151 H3G8XLl0mYN70Y3M1cQF\r
 152 =xbG+\r
 153 -----END PGP SIGNATURE-----\r
 154 \r
 155 --wzJLGUyc3ArbnUjN--\r