From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id EYhGCkDIn18aZQAA0tVLHw (envelope-from ) for ; Mon, 02 Nov 2020 08:50:08 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id 8A7TBUDIn19zLAAA1q6Kng (envelope-from ) for ; Mon, 02 Nov 2020 08:50:08 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [144.217.243.247]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (2048 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id B0F8294021E for ; Mon, 2 Nov 2020 08:50:06 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 3756220013; Mon, 2 Nov 2020 03:49:58 -0500 (EST) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) by mail.notmuchmail.org (Postfix) with ESMTPS id 831AB1F9EC for ; Mon, 2 Nov 2020 03:49:56 -0500 (EST) Received: by mail-wm1-x334.google.com with SMTP id c9so6999637wml.5 for ; Mon, 02 Nov 2020 00:49:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dme-org.20150623.gappssmtp.com; s=20150623; h=to:subject:in-reply-to:references:from:date:message-id:mime-version; bh=u0e0WPVcNvgC9W8hvx9biwoXPTHRoRAgVwZCAR76jEg=; b=RD/Imo00aGgmL9qq+W1XQHTPc8q0KVIMPQq376RITNWe/LLQE+vNQ5zYdtDBs9a040 CMJFFW9Ag03EthOivKROgxJxcHxLNfIAvOcxreQIcjHdl3q0bkUVuBx/4jBNbbVVmILg jd1S9sjJkyVcndMXV2lxnrQ2oZhO7SWMujRuQ3ivD15HTszH/MpZKhPdB7b15gSuaUv5 egOmIxKLZqSzCHcYRddtUaT8JGDpkDBQ7BNb8IjFIa09KtdpOeFdArmps2tz2bvWYx7H 8RlEsm6UHOd3BDJ6Njjn1UA0xFc5mR5SCu7SH8YeN2B9RVdkaDsszWR5E9LR9D/G+LBW 4FeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:subject:in-reply-to:references:from:date :message-id:mime-version; bh=u0e0WPVcNvgC9W8hvx9biwoXPTHRoRAgVwZCAR76jEg=; b=m3RU92RYeSwottGgmtVdxyafO7FNfFowdBq3vwS65jMLhQCoNAFaedLpzg5ZzQ/BPw jmtnd/HWoSJitGuSNPkuNBcyaaD4jzKO5ed52ETcGkMrOONgHwhR1r2j+EBRhFsKqQD+ Gr5/W/vi4q9wFqEx6iNt6/N/cm+zpxLkyE9WmIe+2FSKuUxBMnuKGFrLuaCZsE7wHxhP t4a2PBe/4WOzyQVgQx+QEQDp4PBqn2ZKFDlKR6yAgMWzEJ+yJTjsQGLBJ3tqsMkg3K4u XfDaYEJ19zdeY/1RGq7EKEqgE/fF2OvuiNflGoB98zkuCDh/SkdiKsieiJnEulOcGtGH xenw== X-Gm-Message-State: AOAM532fioy6ljHXZUe4WkYOXXSvzbjR7clUYfN9s5lLmqG1XbOAMs+4 t/DnqciD6/X/i1VRMOGG84HtmA== X-Google-Smtp-Source: ABdhPJwc3RCdLAoRDWMDTKL7Q1drgamc3QV+/H2RKuPZgT6mCvhl0DxxcTNF0tWdiOgNUhPHyt0uRA== X-Received: by 2002:a7b:c11a:: with SMTP id w26mr17181454wmi.78.1604306994758; Mon, 02 Nov 2020 00:49:54 -0800 (PST) Received: from disaster-area.hh.sledj.net (8.a.e.d.0.0.0.0.0.0.0.0.4.6.0.0.0.4.1.7.1.7.b.b.0.b.8.0.1.0.0.2.ip6.arpa. [2001:8b0:bb71:7140:64::dea8]) by smtp.gmail.com with ESMTPSA id g186sm24169302wma.1.2020.11.02.00.49.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Nov 2020 00:49:53 -0800 (PST) Received: from localhost (disaster-area.hh.sledj.net [local]) by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id 0500dc34; Mon, 2 Nov 2020 08:49:53 +0000 (UTC) To: David Mazieres expires 2021-01-31 CET , notmuch@notmuchmail.org Subject: Re: Problems with unicode characters under emacs and Xorg In-Reply-To: <87pn4w9rex.fsf@ta.scs.stanford.edu> References: <87pn4w9rex.fsf@ta.scs.stanford.edu> X-HGTTG: vroomfondel From: David Edmondson Date: Mon, 02 Nov 2020 08:49:53 +0000 Message-ID: MIME-Version: 1.0 Message-ID-Hash: VMECCUQME6ABYEC56BSJUUOXFJ525PEZ X-Message-ID-Hash: VMECCUQME6ABYEC56BSJUUOXFJ525PEZ X-MailFrom: dme@dme.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.1 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=fail (body hash did not verify) header.d=dme-org.20150623.gappssmtp.com header.s=20150623 header.b=RD/Imo00; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 144.217.243.247 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Spam-Score: -0.01 X-TUID: I+m+oge3IsE5 On Sunday, 2020-11-01 at 22:57:58 -08, David Mazieres wrote: > I usually use notmuch in emacs under X windows on arch linux. Recently, > I've had a problem where some screens in notmuch take several minutes of > 100% CPU time to load. For example, I'll just open a search, and emacs > will completely lock up (even Ctrl-G doesn't do anything) for 3 minutes > while my fan spins and my laptop battery drains significantly. > > This appears to be related to the display of certain unicode characters > in email--particularly if they are in the email subject, because then > the whole search screen will freeze. So far, the only workaround I've > found is to kill -15 emacs, start it again in an xterm or urxvt with > "emacs -nw", delete or archive the offending message, and then restart > the Xorg emacs. This is quite painful particularly since it's not > always obvious which email message is causing the problem. > > Has anyone else experienced this problem? Is there any way to > workaround the problem by, for instance, defaulting to unibyte mode for > notmuch buffers? I do use unicode for other languages, but I guess > wouldn't mind having to type "M-x toggle-enable-multibyte-characters" to > get them if as a result my emacs never locked up. > > It's likely that this is an emacs-wide problem, but since whatever these > characters are only show up in email, I'm hoping there are people on > this list who know how to solve the problem or have better workarounds. I haven't seen this. Threads with a lot of complex HTML content (lots of nested tables, for example) can take a long time to render for me, but that is generally interruptable. Could you share one of these messages, or a sufficiently similar test case? dme. -- Driving at 90 down those country lanes, singing to "Tiny Dancer".