GNU bug report logs - #55158
bug: mu/mu4e on Guix does not use correct encoding/utf-8

Previous Next

Package: guix;

Reported by: Benjamin Slade <slade <at> lambda-y.net>

Date: Thu, 28 Apr 2022 00:28:02 UTC

Severity: normal

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 55158 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Benjamin Slade <slade <at> lambda-y.net>, 55158 <at> debbugs.gnu.org
Subject: Re: bug#55158: bug: mu/mu4e on Guix does not use correct
 encoding/utf-8
Date: Sat, 30 Apr 2022 23:11:01 +0200
[Message part 1 (text/plain, inline)]
Benjamin Slade schreef op wo 27-04-2022 om 18:22 [-0600]:
> The output of mu [ <https://guix.gnu.org/en/packages/mu-1.6.10/> ] (and thus, by extension, mu4e in Emacs) does not correctly handle characters outside of a certain range (which confuses Emacs to no end). This behaviour occurs both in mu4e and when using mu on the commandline.
> 
> For instance, subject lines including the 🎉 emoji ("celebration") do not show the emoji, but rather a backslashed \360. Similar issues occur with, for instance, devanagari characters (Hindi etc.).
> 
> When using mu/mu4e on non-Guix systems, this issue does not occur. (I.e. both in mu4e and in mu on the commandline these characters are correctly displayed.)
> 
> Since mu depends on xapian, it's possible the issue could also be with Guix's xapian package.

Does installing glibc-locales + logging in and out again have an
effect?

Greetings,
Maxime.
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 2 years and 351 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.