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


On Aug 10, 2012 7:18 PM, "Jameson Graef Rollins" <jrollins@finestructure.net> wrote:=
>
> On Fri, Aug 10 2012, Jani Nikula <jani@nikula.org> wrote:
> > How would this work together with something like [1] (rationale i= n [2])?
> >
> > [1] id:"ab777cf0fa83778d3399ac52094df9230738= 819d.1328798471.git.jani@nikula.org"
> > [2] id:"cover.1328719309.git.jani@nikula.org"
> >
> > If you introduce a mechanism to store the state, could it be exte= nded to
> > store the state of each individual part? That, in turn, could be = used to
> > add support for expanding/collapsing each alternative part throug= h the
> > buttons (e.g. [ text/html (not shown) ]). Each button could toggl= e the
> > state of the part, and refresh buffer.
>
> Hey, Jani. =C2=A0Are these patches needed if we have Mark's patch?= =C2=A0I would
> prefer to see Mark's solution. =C2=A0Since alternative parts are s= upposed to
> be just that, alternative, it seems to me that a solution that would > cycle through display of these parts is really what we want. =C2=A0Is = there a
> strong need to show multiple alternative parts at the exact same time?=

Thanks to broken Microsoft mail clients, I get plenty of invitations tha= t have text/plain and text/calendar alternative parts with information comp= limenting each other. I usually need to see both (luckily the included html= part I can ignore) and it's helpful if I can see them at the same time= . In a perfect world neither you or me would need any of this functionality= ...

I suppose cycling through the alternative parts is, in a sense, correct = for the reasons you state, we have the code here to do just that, and I can= always cook up something for myself. Let's go with this, then, to move= forward.

BR,
Jani.

--bcaec5523dcc77673d04c6ebfba9--