--- /dev/null
+Return-Path: <jani@nikula.org>\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 4D9B5431FAF\r
+ for <notmuch@notmuchmail.org>; Fri, 10 Aug 2012 09:39:11 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.699\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5\r
+ tests=[HTML_MESSAGE=0.001, 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 1ox1RgUHEDD7 for <notmuch@notmuchmail.org>;\r
+ Fri, 10 Aug 2012 09:39:07 -0700 (PDT)\r
+Received: from mail-qa0-f46.google.com (mail-qa0-f46.google.com\r
+ [209.85.216.46]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 5DCDD431FAE\r
+ for <notmuch@notmuchmail.org>; Fri, 10 Aug 2012 09:39:07 -0700 (PDT)\r
+Received: by qafi31 with SMTP id i31so297969qaf.5\r
+ for <notmuch@notmuchmail.org>; Fri, 10 Aug 2012 09:39:05 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=google.com; s=20120113;\r
+ h=mime-version:in-reply-to:references:date:message-id:subject:from:to\r
+ :cc:content-type:x-gm-message-state;\r
+ bh=DxQev/VIRbpA9igGpBtG5VuWSyIT+tPObERwMnPqRdU=;\r
+ b=OS2lY7iLYYhHdsKhlrXnRqlqAoKo0HlwH+prO1KH/RpOKLALDUoch3ezYy1+xrgj3r\r
+ vUmmyg6Zzq3x0EdX9F4oL0N7beq+iul631vNUDl3TWmwFdX6FVb42+Mn05oyE24nkklK\r
+ 5Qig0af3BAzspes6t9+/TTTCua2I0hBN50Ix9rCzKlQHhvxcpNQzNYmFGCWUTkyeqvfg\r
+ 9JQ3dqODTdQWBi7AbPnCl1x0PBoLJ1V5q1qAsR4hq1LZNCq9zfitLOwPBmXs3Fnf8/ca\r
+ nlo+uYuMa7G4cmOmWTTMmEWJe6EhcWIRF41CK3PRFCvCpKVxYay8jO61/nxsuP2ikpYq\r
+ AzFA==\r
+MIME-Version: 1.0\r
+Received: by 10.60.171.5 with SMTP id aq5mr4939618oec.34.1344616745363; Fri,\r
+ 10 Aug 2012 09:39:05 -0700 (PDT)\r
+Received: by 10.76.151.97 with HTTP; Fri, 10 Aug 2012 09:39:05 -0700 (PDT)\r
+Received: by 10.76.151.97 with HTTP; Fri, 10 Aug 2012 09:39:05 -0700 (PDT)\r
+In-Reply-To: <87wr16u3dj.fsf@servo.finestructure.net>\r
+References: <1339775751-18002-1-git-send-email-jani@nikula.org>\r
+ <87zk80gvmb.fsf@servo.finestructure.net>\r
+ <87pq8vokmp.fsf@qmul.ac.uk>\r
+ <87ipcrvlcw.fsf@servo.finestructure.net>\r
+ <87r4rf9q8x.fsf@qmul.ac.uk> <877gt67q93.fsf@nikula.org>\r
+ <87wr16u3dj.fsf@servo.finestructure.net>\r
+Date: Fri, 10 Aug 2012 19:39:05 +0300\r
+Message-ID:\r
+ <CAB+hUn8kVjasHkD5Wr+MiAvNS4ntVn_A7bfQ-fxuM9_Ob+QqAg@mail.gmail.com>\r
+Subject: Re: [PATCH v2] emacs: add function to toggle display of all\r
+ multipart/alternative parts\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Jameson Graef Rollins <jrollins@finestructure.net>\r
+Content-Type: multipart/alternative; boundary=bcaec5523dcc77673d04c6ebfba9\r
+X-Gm-Message-State:\r
+ ALoCoQnBbQP1rqQjFalxytsvOIW0y9PVVJy1pK5/k33WxY3KsmIypvQH+2rI8qe+7l6PVBGrwzmn\r
+Cc: Notmuch Mail <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: Fri, 10 Aug 2012 16:39:11 -0000\r
+\r
+--bcaec5523dcc77673d04c6ebfba9\r
+Content-Type: text/plain; charset=UTF-8\r
+\r
+On Aug 10, 2012 7:18 PM, "Jameson Graef Rollins" <jrollins@finestructure.net>\r
+wrote:\r
+>\r
+> On Fri, Aug 10 2012, Jani Nikula <jani@nikula.org> wrote:\r
+> > How would this work together with something like [1] (rationale in [2])?\r
+> >\r
+> > [1] id:"\r
+ab777cf0fa83778d3399ac52094df9230738819d.1328798471.git.jani@nikula.org"\r
+> > [2] id:"cover.1328719309.git.jani@nikula.org"\r
+> >\r
+> > If you introduce a mechanism to store the state, could it be extended to\r
+> > store the state of each individual part? That, in turn, could be used to\r
+> > add support for expanding/collapsing each alternative part through the\r
+> > buttons (e.g. [ text/html (not shown) ]). Each button could toggle the\r
+> > state of the part, and refresh buffer.\r
+>\r
+> Hey, Jani. Are these patches needed if we have Mark's patch? I would\r
+> prefer to see Mark's solution. Since alternative parts are supposed to\r
+> be just that, alternative, it seems to me that a solution that would\r
+> cycle through display of these parts is really what we want. Is there a\r
+> strong need to show multiple alternative parts at the exact same time?\r
+\r
+Thanks to broken Microsoft mail clients, I get plenty of invitations that\r
+have text/plain and text/calendar alternative parts with information\r
+complimenting each other. I usually need to see both (luckily the included\r
+html part I can ignore) and it's helpful if I can see them at the same\r
+time. In a perfect world neither you or me would need any of this\r
+functionality...\r
+\r
+I suppose cycling through the alternative parts is, in a sense, correct for\r
+the reasons you state, we have the code here to do just that, and I can\r
+always cook up something for myself. Let's go with this, then, to move\r
+forward.\r
+\r
+BR,\r
+Jani.\r
+\r
+--bcaec5523dcc77673d04c6ebfba9\r
+Content-Type: text/html; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<p><br>\r
+On Aug 10, 2012 7:18 PM, "Jameson Graef Rollins" <<a href=3D"m=\r
+ailto:jrollins@finestructure.net">jrollins@finestructure.net</a>> wrote:=\r
+<br>\r
+><br>\r
+> On Fri, Aug 10 2012, Jani Nikula <<a href=3D"mailto:jani@nikula.org=\r
+">jani@nikula.org</a>> wrote:<br>\r
+> > How would this work together with something like [1] (rationale i=\r
+n [2])?<br>\r
+> ><br>\r
+> > [1] id:"<a href=3D"mailto:ab777cf0fa83778d3399ac52094df92307=\r
+38819d.1328798471.git.jani@nikula.org">ab777cf0fa83778d3399ac52094df9230738=\r
+819d.1328798471.git.jani@nikula.org</a>"<br>\r
+> > [2] id:"<a href=3D"mailto:cover.1328719309.git.jani@nikula.o=\r
+rg">cover.1328719309.git.jani@nikula.org</a>"<br>\r
+> ><br>\r
+> > If you introduce a mechanism to store the state, could it be exte=\r
+nded to<br>\r
+> > store the state of each individual part? That, in turn, could be =\r
+used to<br>\r
+> > add support for expanding/collapsing each alternative part throug=\r
+h the<br>\r
+> > buttons (e.g. [ text/html (not shown) ]). Each button could toggl=\r
+e the<br>\r
+> > state of the part, and refresh buffer.<br>\r
+><br>\r
+> Hey, Jani. =C2=A0Are these patches needed if we have Mark's patch?=\r
+ =C2=A0I would<br>\r
+> prefer to see Mark's solution. =C2=A0Since alternative parts are s=\r
+upposed to<br>\r
+> be just that, alternative, it seems to me that a solution that would<b=\r
+r>\r
+> cycle through display of these parts is really what we want. =C2=A0Is =\r
+there a<br>\r
+> strong need to show multiple alternative parts at the exact same time?=\r
+</p>\r
+<p>Thanks to broken Microsoft mail clients, I get plenty of invitations tha=\r
+t have text/plain and text/calendar alternative parts with information comp=\r
+limenting each other. I usually need to see both (luckily the included html=\r
+ part I can ignore) and it's helpful if I can see them at the same time=\r
+. In a perfect world neither you or me would need any of this functionality=\r
+...</p>\r
+\r
+<p>I suppose cycling through the alternative parts is, in a sense, correct =\r
+for the reasons you state, we have the code here to do just that, and I can=\r
+ always cook up something for myself. Let's go with this, then, to move=\r
+ forward.</p>\r
+\r
+<p>BR,<br>\r
+Jani.</p>\r
+\r
+--bcaec5523dcc77673d04c6ebfba9--\r