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 OKkoD9uvn18TIwAA0tVLHw (envelope-from ) for ; Mon, 02 Nov 2020 07:06:03 +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 aJPvCtuvn19IWQAA1q6Kng (envelope-from ) for ; Mon, 02 Nov 2020 07:06:03 +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 7AC2394021E for ; Mon, 2 Nov 2020 07:06:00 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 94AD720013; Mon, 2 Nov 2020 02:05:50 -0500 (EST) X-Greylist: delayed 466 seconds by postgrey-1.36 at nmbug; Mon, 02 Nov 2020 02:05:46 EST Received: from market.scs.stanford.edu (www.scs.stanford.edu [IPv6:2001:470:806d:1::9]) by mail.notmuchmail.org (Postfix) with ESMTPS id E16371FFF8 for ; Mon, 2 Nov 2020 02:05:46 -0500 (EST) Received: from market.scs.stanford.edu (localhost [127.0.0.1]) by market.scs.stanford.edu (8.16.0.45/8.16.0.45) with ESMTP id 0A26vxxY027779 for ; Sun, 1 Nov 2020 22:57:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scs.stanford.edu; s=scs; t=1604300279; bh=SdDxjg5fUdUgOQY/zqWBjuxGBxNFRs5ond0rM1xiu5A=; h=From:To:Subject:Date:Message-ID:MIME-Version; b=QcW8epOIfqlZqZTGsAnFl9JhqDw6yHCHJ/3wzkkq+TE3Gv7eoWbtujJHphJkHf+Tr qOPtqPRdxCkIp+m3LmFGlxKBXoMYW+Krql9IBCsxQryvP4WwtL3ZqBEsVJE636VOc8 SVbAHUBk22APqVfkejOIRDikYKRKcn/JeMchkHWc= Received: (from dm@localhost) by market.scs.stanford.edu (8.16.0.45/8.16.0.45/Submit) id 0A26vvoX086260; Sun, 1 Nov 2020 22:57:57 -0800 (PST) From: David Mazieres To: notmuch@notmuchmail.org Subject: Problems with unicode characters under emacs and Xorg Date: Sun, 01 Nov 2020 22:57:58 -0800 Message-ID: <87pn4w9rex.fsf@ta.scs.stanford.edu> MIME-Version: 1.0 Message-ID-Hash: PWM2UQ5M6R7YDRNCKMRSRMHO2RR3WPNA X-Message-ID-Hash: PWM2UQ5M6R7YDRNCKMRSRMHO2RR3WPNA X-MailFrom: return-w7tknviwpij9q63undx4fgnyan@temporary-address.scs.stanford.edu 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 Reply-To: David Mazieres expires 2021-01-31 CET 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=scs.stanford.edu header.s=scs header.b=QcW8epOI; 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: bfAmioaq268x 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. Thanks, David