From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 5B5866DE0361 for ; Fri, 18 Jan 2019 16:11:32 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -2.482 X-Spam-Level: X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=-0.086, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FROM_EXCESS_BASE64=0.105, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u_HWP41Agqhj for ; Fri, 18 Jan 2019 16:11:29 -0800 (PST) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) by arlo.cworth.org (Postfix) with ESMTPS id 674D06DE02DD for ; Fri, 18 Jan 2019 16:11:29 -0800 (PST) Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id E8D7416005D for ; Sat, 19 Jan 2019 01:11:25 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1547856685; bh=zL2NaUtqKuTn/O7tZ7l5oHPTQQV/8nYk5d+xipAbQNA=; h=From:To:Subject:Date:From; b=rwcIKf4W704cM6k/1yTFEmNkUe4iQte03K8nc/tTK65mr1gCO/tVF/IR5sLgfY1pV vcUiq/RIOZ4GB8chF83p3LnAtVEPmlqDW7ZMkfRO7K0Yl2SzPbt7Iqku5sW2NNNe4k O6gjiL0/px//iS2uysxX1t12psSQ1n639TpiyyQboP3L6TGgy17JFmau8qNDJSaqSi n4cI4UqKk6gFGadoK4KVfL3H3V2W5IX4tu+qXfwvlKH6YH3GG3/FkbfI0DZJnLSi9j f4/Cj5wV6VvI8BrrPWHvlik1uUdXLwwR9AxZio/anpWfLUwLlAyPKJAuepSMvmZ8DQ H/XefAGvfSS8w== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 43hJBj2wnLz6tmB for ; Sat, 19 Jan 2019 01:11:24 +0100 (CET) From: Dan =?utf-8?B?xIxlcm3DoWs=?= To: "notmuch\@notmuchmail.org" Subject: Re: emacs slow with large threads In-Reply-To: <87fttpy0n5.fsf@mechane.wlandry.net> References: <87fttpy0n5.fsf@mechane.wlandry.net> Date: Sat, 19 Jan 2019 01:11:20 +0100 Message-ID: <878szh8q1j.fsf@cgc-instruments.com> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Sat, 19 Jan 2019 00:11:32 -0000 Hi Landry, I am afraid this is a common limitation of emacs: if you start opening large files (especially with long lines) it becomes very slow. A viable workaround is to open the offending thread in the tree view (bound to 'z' by default) and then only view individual messages. Cheers, Dan "Landry, Walter" writes: > Hello Everyone, > > I am using the emacs frontend to notmuch. It has mostly been a pleasant > experience, but I am having a problem with large threads. Essentially, > when I try to view a large thread, the machine locks up for many > minutes. The problem seems very similar to these posts. > > https://notmuchmail.org/pipermail/notmuch/2013/014811.html > https://notmuchmail.org/pipermail/notmuch/2015/020379.html > > I tried turning off html rendering by setting mm-text-html-renderer to > nil. That helped, but it is still taking at least 10 minutes to render > a thread. I killed it when I ran out of patience. > > The thread has 231 messages, and running > > notmuch show thread:000000000000d637 | wc -l > > shows that it is 46918 lines long. Running that on the command line is > fast, taking 0.123 seconds. As a comparison, I tried opening the thread > with astroid. It was not instantaneous, but it only took about 3 > seconds. > > I am guessing that the emacs mode is trying to process the result. I > can work around this a bit by opening individual messages with "C-u RET" > instead of "RET". But then I lose context. > > Is there anything else I can do to make this work? > > Thanks, > Walter Landry > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch