From: David Edmondson <dme@dme.org>
To: David Mazieres expires 2021-01-31 CET
<mazieres-iy7w9kq655nsh7jm22hqaqgrvs@temporary-address.scs.stanford.edu>,
notmuch@notmuchmail.org
Subject: Re: Problems with unicode characters under emacs and Xorg
Date: Mon, 02 Nov 2020 08:49:53 +0000 [thread overview]
Message-ID: <cunk0v42le6.fsf@vroomfondel.hh.sledj.net> (raw)
In-Reply-To: <87pn4w9rex.fsf@ta.scs.stanford.edu>
On Sunday, 2020-11-01 at 22:57:58 -08, David Mazieres wrote:
> 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.
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?
dme.
--
Driving at 90 down those country lanes, singing to "Tiny Dancer".
next prev parent reply other threads:[~2020-11-02 8:50 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 [this message]
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
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=cunk0v42le6.fsf@vroomfondel.hh.sledj.net \
--to=dme@dme.org \
--cc=mazieres-iy7w9kq655nsh7jm22hqaqgrvs@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).