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 6E9754196F3 for ; Thu, 22 Apr 2010 07:10:20 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.1 X-Spam-Level: X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001] autolearn=ham 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 Ck4Uu5xrtsnc for ; Thu, 22 Apr 2010 07:10:18 -0700 (PDT) Received: from mail-wy0-f181.google.com (mail-wy0-f181.google.com [74.125.82.181]) by olra.theworths.org (Postfix) with ESMTP id 690AE431FC1 for ; Thu, 22 Apr 2010 07:10:18 -0700 (PDT) Received: by wyf23 with SMTP id 23so752193wyf.26 for ; Thu, 22 Apr 2010 07:10:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type; bh=II59ct3JxT4Uf34rvoySCi+MMKWcpNKYRUZsPGgeqek=; b=UcriAJJoDZiyyG9Y5Xb6LcbyLmA2TgQMyy3u/x0feP9lNJ4sD9f2vxDZgf/Wremi5c uj2KlIMMDBMFZ8FOck8uEHUU2+bkRMia4GH/ox/DLQ0Ol+JrzEwDbGPdArXrs1CFLGdo FybWyIU9W4lLSKzebN37JQHpCCoFCDLyDjWOY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Nt8K++tbW2p/7OzgUXILFzRYCgs+FoU9CbtTR1QvA6n6sTRFFZcmhBtmUetJvQ8yra xJh4AUbQZjnUg5+ap0x4Y1Z4+EjotlCd5E8BmDthjvV7KhSroUZctNBIYYqYQxTbOxRk lMY6uHqsrlABPDp84hcRWD4WWY61qKf4IZ5p8= MIME-Version: 1.0 Received: by 10.216.133.155 with HTTP; Thu, 22 Apr 2010 07:10:15 -0700 (PDT) In-Reply-To: <87aasvk6tx.fsf@ut.hh.sledj.net> References: <87sk722sfq.fsf@ut.hh.sledj.net> <87eiibq22s.fsf@ut.hh.sledj.net> <87iq7kjz7c.fsf@yoom.home.cworth.org> <87aasvk6tx.fsf@ut.hh.sledj.net> Date: Thu, 22 Apr 2010 10:10:15 -0400 Received: by 10.216.86.212 with SMTP id w62mr2708510wee.131.1271945416737; Thu, 22 Apr 2010 07:10:16 -0700 (PDT) Message-ID: Subject: Re: pull request From: Servilio Afre Puentes To: David Edmondson Content-Type: text/plain; charset=ISO-8859-1 Cc: notmuch 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, 22 Apr 2010 14:10:20 -0000 On 22 April 2010 08:30, David Edmondson wrote: > On Thu, 22 Apr 2010 04:58:16 -0400, Servilio Afre Puentes wrote: >> On 21 April 2010 17:03, Carl Worth wrote: >> > On Mon, 19 Apr 2010 09:27:39 +0100, David Edmondson wrote: >> [...] >> > Meanwhile, another issue with the result of this series is that I now >> > seem to get rendering for both the text/plain and the text/html >> > alternatives when a message has both. For now, the paragraphs are >> > wrapped much more nicely in the rendering of the html portion, but links >> > are apparently entirely missing. The link URLs at least appear in the >> > text/plain rendering, (which is pretty ugly, but at least not impossible >> > to use). >> > >> > If we could get one version or the other working completely, then it >> > would be nice to display only one. >> >> I think that a better approach here would be to list them as parts if >> they are present, then have a [configurable] way to show only one by >> default, and the other would be available to show in-line. > > Showing only one (with a variable allowing you to express preference) is > my intention. Any non-shown parts will appear as attachments - you can > save them using the button (and perhaps later view them). Why not see them in-line if possible? > This can make quite a big difference in a 200 message thread with lots > of 'text/plain or text/html ?' choices - using the text/plain part will > improve the performance of building the show buffer significantly. Yes, it can make a big difference. >> What I miss in this view sometimes is the possibility of being able to >> see the structure of the thread. A way to toggle the expanded state of >> the messages originally expanded when I first opened the view would do >> this very nicely. > > Ah, so you want a "go back to how it was initially" command? Yep, then bind it to a key that would alternate between collapsing all messages and expanding the ones that were originally expanded. Servilio