From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id oHEBCzH9n19WOQAA0tVLHw (envelope-from ) for ; Mon, 02 Nov 2020 12:36:01 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id s5TwBjH9n19ASAAAB5/wlQ (envelope-from ) for ; Mon, 02 Nov 2020 12:36:01 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [IPv6:2607:5300:201:3100::1657]) (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 4B0489407C8 for ; Mon, 2 Nov 2020 12:36:00 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 1334920315; Mon, 2 Nov 2020 07:35:51 -0500 (EST) X-Greylist: delayed 559 seconds by postgrey-1.36 at nmbug; Mon, 02 Nov 2020 07:35:48 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 4BDA21F9EC for ; Mon, 2 Nov 2020 07:35:48 -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 0A2CQRrM097801; Mon, 2 Nov 2020 04:26:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scs.stanford.edu; s=scs; t=1604319987; bh=jtOpBwHs9amKS2Q2xkZx5fjxUWnLCi9c9n+pFPiRFN0=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version; b=EsRwqfu4i6fctHaqMeXW/JlmP6htqSH/ux/qWoigLWAUQTd9DdKZBTUDybggQ1DCc hZG10PG14gE1v5MdDejm8POEugsVUk+kYIUGfkvjyG9opr8zSDaJu8Ohei4XCa5UaV v7ntj51xKo3X0dOmlYejG5M2ZlJ7g3ypYl23O6Zs= Received: (from dm@localhost) by market.scs.stanford.edu (8.16.0.45/8.16.0.45/Submit) id 0A2CQRox007263; Mon, 2 Nov 2020 04:26:27 -0800 (PST) From: David Mazieres To: David Edmondson , notmuch@notmuchmail.org Subject: Re: Problems with unicode characters under emacs and Xorg In-Reply-To: <875z6orqvb.fsf@ta.scs.stanford.edu> References: <87pn4w9rex.fsf@ta.scs.stanford.edu> <87o8kg15dv.fsf@ta.scs.stanford.edu> <875z6orqvb.fsf@ta.scs.stanford.edu> Date: Mon, 02 Nov 2020 04:26:27 -0800 Message-ID: <87tuu8ueq4.fsf@ta.scs.stanford.edu> MIME-Version: 1.0 Message-ID-Hash: MM2XNC4YFAVOBQEWJVA3FDDYILTQJJT4 X-Message-ID-Hash: MM2XNC4YFAVOBQEWJVA3FDDYILTQJJT4 X-MailFrom: return-ciabxkir9emykmrmm4gdh7mw7a@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=EsRwqfu4; dmarc=none; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2607:5300:201:3100::1657 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Spam-Score: -0.01 X-TUID: tOjRBeIRNkwY dm-list-email-notmuch@scs.stanford.edu writes: > I just installed the ttf-symbola package from AUR and ran fc-cache (not > sure if necessary). Now the problem is completely gone. Not only that, > but I even get the little memo symbol instead of a box with the hex code > point number. > > Thank you so much! This was driving me nuts for months. Sadly, I spoke too soon. This does fix the particular problem that I posted, and makes the situation better, but I'm still getting occasional lockups, presumably because symbola does not cover every possible symbol. For example, I had another email containing U+8BDD (CJK UNIFIED IDEOGRAPH-8BDD), and this one still caused my emacs to spin for many minutes, before displaying a box with 8BDD in it. So unfortunately the problem seems to be that any character not supported by an installed font takes about 2-5 minutes of CPU time to resolve. And of course most characters that I'd use are in installed fonts, except that I can control what's in the emails I receive, so this makes notmuch very painful to use. But if no one else is running into the problems, then I may be able to get around it by installing whatever fonts other people have installed. Thanks, David