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 14EE0431E82 for ; Tue, 24 Mar 2015 12:45:13 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 2.438 X-Spam-Level: ** X-Spam-Status: No, score=2.438 tagged_above=-999 required=5 tests=[DNS_FROM_AHBL_RHSBL=2.438] 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 BlT+7aqTO-b6 for ; Tue, 24 Mar 2015 12:45:09 -0700 (PDT) Received: from mx.xen14.node3324.gplhost.com (gitolite.debian.net [87.98.215.224]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id C2899431E62 for ; Tue, 24 Mar 2015 12:45:09 -0700 (PDT) Received: from remotemail by mx.xen14.node3324.gplhost.com with local (Exim 4.80) (envelope-from ) id 1YaUjr-0001yM-Dp; Tue, 24 Mar 2015 19:43:47 +0000 Received: (nullmailer pid 12997 invoked by uid 1000); Tue, 24 Mar 2015 19:43:36 -0000 From: David Bremner To: Jed Brown , Michael Hudson-Doyle Subject: Re: Emacs client scalability for long, deeply-nested threads In-Reply-To: <874mpb5m80.fsf@jedbrown.org> References: <87sicv60xn.fsf@jedbrown.org> <874mpb5m80.fsf@jedbrown.org> User-Agent: Notmuch/0.19+86~gbed8b67 (http://notmuchmail.org) Emacs/24.4.1 (x86_64-pc-linux-gnu) Date: Tue, 24 Mar 2015 15:43:36 -0400 Message-ID: <878uem6v13.fsf@maritornes.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain 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: Tue, 24 Mar 2015 19:45:13 -0000 Jed Brown writes: > Michael Hudson-Doyle writes: > >> I have encountered this too. A C-u before entering the thread helps >> (this means already read messages are not rendered I think), as does a >> M-x notmuch-show-toggle-thread-indentation . > > Thanks, Michael. This does help, though it makes it hard to interpret > context. I'd love a solution that does not degrade utility so > drastically. How is the performance of tree-view on these threads? d