--- /dev/null
+Return-Path: <jrollins@finestructure.net>\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 DAC67431FAE\r
+ for <notmuch@notmuchmail.org>; Mon, 13 Aug 2012 09:58:54 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.29\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_MED=-2.3, T_MIME_NO_TEXT=0.01] 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 y6brprKkHX90 for <notmuch@notmuchmail.org>;\r
+ Mon, 13 Aug 2012 09:58:52 -0700 (PDT)\r
+Received: from outgoing-mail.its.caltech.edu (outgoing-mail.its.caltech.edu\r
+ [131.215.239.19])\r
+ by olra.theworths.org (Postfix) with ESMTP id B56D1431FC0\r
+ for <notmuch@notmuchmail.org>; Mon, 13 Aug 2012 09:58:52 -0700 (PDT)\r
+Received: from fire-doxen.imss.caltech.edu (localhost [127.0.0.1])\r
+ by fire-doxen-postvirus (Postfix) with ESMTP id 5EEF132801F;\r
+ Mon, 13 Aug 2012 09:58:50 -0700 (PDT)\r
+X-Spam-Scanned: at Caltech-IMSS on fire-doxen by amavisd-new\r
+Received: from finestructure.net (adsl-76-240-184-246.dsl.irvnca.sbcglobal.net\r
+ [76.240.184.246]) (Authenticated sender: jrollins)\r
+ by fire-doxen-submit (Postfix) with ESMTP id 560442E50D8C;\r
+ Mon, 13 Aug 2012 09:58:47 -0700 (PDT)\r
+Received: by finestructure.net (Postfix, from userid 1000)\r
+ id 2DD00547; Mon, 13 Aug 2012 09:48:54 -0700 (PDT)\r
+From: Jameson Graef Rollins <jrollins@finestructure.net>\r
+To: hellekin <hellekin@cepheide.org>, notmuch@notmuchmail.org\r
+Subject: Re: multipart/alternative bug\r
+In-Reply-To: <sa87gt294f7.fsf@retro.synap.tk>\r
+References: <sa87gt294f7.fsf@retro.synap.tk>\r
+User-Agent: Notmuch/0.13.2+137~ge34ed71 (http://notmuchmail.org) Emacs/23.4.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Mon, 13 Aug 2012 09:48:51 -0700\r
+Message-ID: <87ipcmspos.fsf@servo.finestructure.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+ micalg=pgp-sha256; protocol="application/pgp-signature"\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: Mon, 13 Aug 2012 16:58:55 -0000\r
+\r
+--=-=-=\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+On Mon, Aug 13 2012, hellekin <hellekin@cepheide.org> wrote:\r
+> as I mentioned on IRC a few days ago, there are some cases where:\r
+>\r
+> - a thread only displays the first message\r
+> - key bindings do not work at all (except q)\r
+>\r
+> By trial and error, I could nail down the issue to multipart/alternative\r
+> support. I had set notmuch to only show the text/plain part of an email\r
+> before hitting the bug, and by setting "Notmuch Show All\r
+> Multipart/Alternative Parts" to *off* in notmuch-show configuration, the\r
+> bug disappeared.=20\r
+>\r
+> I'm sorry not to be able to dig further, but I hope this tip will help\r
+> users to avoid the issue, and developers to find and fix the bug.\r
+\r
+Hi, hk. I'm going to go out on a limb and guess that this is actually\r
+probably *not* an issue with multipart/alternative but instead with\r
+whatever is in that alternative part. If you set\r
+notmuch-show-all-multipart/alternative to off you're only seeing the\r
+text/plain part. If there's something crazy in the alternative part,\r
+something that's not getting decoded correctly maybe, then that might\r
+screw up the buffer.\r
+\r
+Can you use the command line UI to determine what else is in the\r
+offending message? Is it just a text/html part, or is there something\r
+else more exotic? A lot of popular but broken MUAs stuff\r
+non-alternative stuff into alternative parts.\r
+\r
+You can grab the message id (id:XXX) of the offending message with 'c i'\r
+in the emacs UI, and the look at it on the command line with:\r
+\r
+notmuch show id:XXX\r
+\r
+hth.\r
+\r
+jamie.\r
+\r
+ps. In general the command line UI is a great resource for figuring out\r
+what might be causing problems in the emacs UI.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.12 (GNU/Linux)\r
+\r
+iQIcBAEBCAAGBQJQKS/zAAoJEO00zqvie6q86ckP/2s07/2spEBHc5EP3ve0raud\r
+xab6FNpA7LHFmAbKhV1zdLAbpIBCQQr/YtmBLXntZiwSi5QlVPQ0nUcpOVZxBMde\r
+nDtrQw2k8X932ZBRUR5Dh6ou7suevjAbEslU7j4Qi0n+Ml80fcmtS9UIWg8DJERA\r
+xq81CaJ0Gb582OOPjIxgfuCBDSUpAnNFnro8ohvyYHpEdf9j26SXti/g3jPgubqE\r
+yotl7HDIENmgVEE9CGVAjIPilkJxQt5OHkmSNVQ4vAK+lHGBKfVZ347zsMDXW46q\r
+R0rBMq4FDCzv5vG9T4FQhB09+bJ9BFq+gDY6HKSTm1ZFE+GZsrqQ/8EaDQa4xB1a\r
+sW1FcUi1Wbew2s2FepAV/DybwNy4GhdE4HqJUsohlq7I5m+jli9v6pH5c3gCWt3b\r
+ub4NaOrkL+qhbcA+1SCglIV2I/wznBAJH8k9d2PRA+eMQGRgLyTYWQk4ClCjTI0z\r
+0Y2YI2UpwHgRI7JDclLPTRBD0Swjan/Dj96NIFK19FN5E/TlkE9yzCg1EofSla3d\r
+POZxtJ64Z8g+mcEUX7O1tTelDTFHUShL71h2JAYwsEPHEgRR4IOLYbSQYguWkNot\r
+Agqj2rMm3x1XaBt9bmCpoVMelLLHeKObkbb61slUUfE4+mK7qT36QWUFauP37hls\r
+iJFVtNKhNKgXTPfNRH3p\r
+=vvH2\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r