From: dm-list-email-notmuch@scs.stanford.edu
To: David Edmondson <dme@dme.org>, notmuch@notmuchmail.org
Subject: Re: Problems with unicode characters under emacs and Xorg
Date: Mon, 02 Nov 2020 01:21:00 -0800 [thread overview]
Message-ID: <87o8kg15dv.fsf@ta.scs.stanford.edu> (raw)
In-Reply-To: <cunk0v42le6.fsf@vroomfondel.hh.sledj.net>
David Edmondson <dme@dme.org> 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
next prev parent reply other threads:[~2020-11-02 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 6:57 Problems with unicode characters under emacs and Xorg David Mazieres
2020-11-02 8:49 ` David Edmondson
2020-11-02 9:21 ` dm-list-email-notmuch [this message]
2020-11-02 10:09 ` David Edmondson
2020-11-02 10:32 ` dm-list-email-notmuch
2020-11-02 12:26 ` David Mazieres
2020-11-02 12:55 ` David Edmondson
2020-11-03 21:59 ` Tomi Ollila
2020-11-03 22:19 ` dm-list-email-notmuch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8kg15dv.fsf@ta.scs.stanford.edu \
--to=dm-list-email-notmuch@scs.stanford.edu \
--cc=dme@dme.org \
--cc=mazieres-z2z3si8gksd2wu49pq2srsd9ae@temporary-address.scs.stanford.edu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).