unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Edmondson <dme@dme.org>
To: David Mazieres expires 2021-01-31 CET
	<mazieres-hedmzjc3jh3b5bny5ejik96xv6@temporary-address.scs.stanford.edu>,
	notmuch@notmuchmail.org
Subject: Re: Problems with unicode characters under emacs and Xorg
Date: Mon, 02 Nov 2020 12:55:59 +0000	[thread overview]
Message-ID: <cund00v3okg.fsf@vroomfondel.hh.sledj.net> (raw)
In-Reply-To: <87tuu8ueq4.fsf@ta.scs.stanford.edu>

On Monday, 2020-11-02 at 04:26:27 -08, David Mazieres wrote:

> 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.

That one is from:

-isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0

though I'm not sure which package provides that.

> 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.

I don't seem to have the root problem - that unknown characters cause a
delay. I get the hex-filled box immediately.

dme.
-- 
Maybe then I'll fade away and not have to face the facts.

  reply	other threads:[~2020-11-02 12:56 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
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 [this message]
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=cund00v3okg.fsf@vroomfondel.hh.sledj.net \
    --to=dme@dme.org \
    --cc=mazieres-hedmzjc3jh3b5bny5ejik96xv6@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).