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 Jm7dCQDTn189RwAA0tVLHw (envelope-from ) for ; Mon, 02 Nov 2020 09:36:00 +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 vzzDBQDTn18cTgAA1q6Kng (envelope-from ) for ; Mon, 02 Nov 2020 09:36:00 +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 1DC63940149 for ; Mon, 2 Nov 2020 09:35:59 +0000 (UTC) Received: from nmbug.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 7216E20315; Mon, 2 Nov 2020 04:35:50 -0500 (EST) X-Greylist: delayed 885 seconds by postgrey-1.36 at nmbug; Mon, 02 Nov 2020 04:35:47 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 9C8441F9E9 for ; Mon, 2 Nov 2020 04:35:47 -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 0A29L0dc052306; Mon, 2 Nov 2020 01:21:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=scs.stanford.edu; s=scs; t=1604308860; bh=b7Ju5PCJLEqpUymqfhUyB7D1I6t6ofFy8X5Z/aYMsdE=; h=From:To:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version; b=Qf9QmZ5RBdctn4rVr8jZetGToo/Qrk+aljIjfwpsTFjmhsTFe2k+sBJqMB2FD8FLQ WfUsAsGqDsLEaXgOR63XAgS/+k5gQPXXq2zJQVLcVb8ISMFmPrYxnDdlvwFn38GZ3z qyNfcJeh6zsD/wIPQRy+Zey09GNgGEwRXSU2550Q= Received: (from dm@localhost) by market.scs.stanford.edu (8.16.0.45/8.16.0.45/Submit) id 0A29KxXL042189; Mon, 2 Nov 2020 01:20:59 -0800 (PST) From: dm-list-email-notmuch@scs.stanford.edu To: David Edmondson , notmuch@notmuchmail.org Subject: Re: Problems with unicode characters under emacs and Xorg In-Reply-To: References: <87pn4w9rex.fsf@ta.scs.stanford.edu> Date: Mon, 02 Nov 2020 01:21:00 -0800 Message-ID: <87o8kg15dv.fsf@ta.scs.stanford.edu> MIME-Version: 1.0 Message-ID-Hash: NDXK6MJK6ULXXPGE4FGAUF5HDF6ZPZOZ X-Message-ID-Hash: NDXK6MJK6ULXXPGE4FGAUF5HDF6ZPZOZ X-MailFrom: return-6zsyajejq5yn7mste9ak5kjrdn@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=Qf9QmZ5R; 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: CHdE4q78MMYn David Edmondson writes: > 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? Thanks for the reply. I can send one of these emails to you privately if necessary, as it might contain semi-sensitive information. However, I think all you need is the subject line. For example: Subject: =?UTF-8?B?RGF2aWQ6IEhvdy1UbyBIaXJlIHRoZSBCZXN0IFJlbW9kZWxpbmcgQ29udHJhY3RvciDwn5Od?= That subject line alone triggers the problem, because any search returning that thread triggers the problem. When decoded, the subject line ends with unicode code point 0x1F4DD (MEMO). Indeed, if I open up a fresh emacs, and, independent of notmuch, type "C-x 8 RET memo RET", it causes the emacs to hang for a minute or so. Arguably this is a limitation of emacs or fontconfig, or I've installed too many fonts on my system, or I've installed too few fonts (because after all that computation it just renders a box with hext digits 01F4DD in it instead of showing the MEMO icon). However, the problem only happens with notmuch, because notmuch is the only emacs functionality I need that renders anything other than a very limited set of unicode characters. So if there's any way either to workaround the problem, or to copy whatever other notmuch users are doing (is there some particular unicode font I should just install on my system?), I would be very happy. Thanks, David