From: Wenlong Dai <whudwl@gmail.com>
To: notmuch@notmuchmail.org
Subject: Why some characters are not displayed correctly when setting mm-text-html-renderer to links
Date: Tue, 17 Nov 2020 02:00:09 +1100 [thread overview]
Message-ID: <CADmxP+MiVZmjwq-qGcS+b9AJkZWUuFeQQHK7cVbyQeYEvXgL0Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1289 bytes --]
I'm using gccemcs under WSL2 and trying to switch from mu4e to notmuch.
One thing I immediately like about notmuch is that it's much more faster
than mu4e.
But I also almost immediately ran into some issues. The one that bothers me
the most is,
when I hit ENTER to open a long thread from notmuch-search mode, it takes a
very long time to load.
Sometimes, this can take 30 seconds or more. My understanding is that
notmuch needs to load all the messages
(in my case, I tried threads with 20+ messages), and the default shr
renderer is not great at dealing with large amount of data.
After some research, I found that setting mm-text-html-renderer to links
would reduce the load time from <a long time>
to around 2 seconds or less. But one small issue with this is some
characters are not displayed correctly, for example the
RIGHT SINGLE QUOTATION MARK, which would be displayed as \342\200\231
A bit more research lead me to the toggle-enable-multibyte-characters
function, I found that if I invoke this function
twice interactively, the display would be fixed.
I guess my question is, how do I make notmuch-show display characters like
RIGHT SINGLE QUOTATION MARK correctly
when I use links as html renderer? And why would invoking
toggle-enable-multibyte-characters fix the issue?
[-- Attachment #1.2: Type: text/html, Size: 3240 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2020-11-16 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:00 Wenlong Dai [this message]
2021-08-06 18:47 ` Why some characters are not displayed correctly when setting mm-text-html-renderer to links David Bremner
2021-08-09 20:13 ` Tomi Ollila
2021-09-26 11:24 ` David Bremner
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=CADmxP+MiVZmjwq-qGcS+b9AJkZWUuFeQQHK7cVbyQeYEvXgL0Q@mail.gmail.com \
--to=whudwl@gmail.com \
--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).