Inverted text in mu-article and mu-headers

5 views
Skip to first unread message

jman

unread,
Jul 31, 2025, 4:58:56 PMJul 31
to 'jman' via mu-discuss

Hello,

I received a notification from github and the text looks quite interesting.
In both the mu-article and mu-headers buffers the text is mirrored. Seems like there's something
telling mu4e to read the text RTL (Right-To-Left).
I'm curious if anyone can reproduce this. Or is it just me? Only seen in this email, never seen
anything like that. So I *think* it hasn't to do with my setup.

Email text
https://paste.debian.net/hidden/73e79326/

Screenshot of how I see in mu4e
https://pasteboard.co/Egz9iUfTjARK.png

I'm using latest mu4e 1.12.9 on Debian/trixie

Thanks

Jorge Javier Araya Navarro

unread,
Aug 1, 2025, 2:14:52 AMAug 1
to mu-di...@googlegroups.com
This is my setup for mu4e:
https://gitlab.com/shackra/emacs/-/blob/master/email.el?ref_type=heads

Text looks okay on my end. What's your font and what's your mother
tongue?
--
Jorge Araya

Contacto:
Telegram: t.me/shackra · Signal: Shackra.28

jman

unread,
Aug 2, 2025, 5:20:48 AMAug 2
to Jorge Javier Araya Navarro, mu-di...@googlegroups.com
Jorge Javier Araya Navarro <shackra...@gmail.com> writes:

> This is my setup for mu4e:
> https://gitlab.com/shackra/emacs/-/blob/master/email.el?ref_type=heads
>
> Text looks okay on my end. What's your font and what's your mother
> tongue?

I'm not sure I can answer these questions. What do you mean by "font"? System font or emacs font? I
have a Linux operating system completely in American English, I use emacs without GUI and no `(setq
set-face)` anywhere. I think I don't have any package installed that could be related to RTL text.

What I probably need is some tips on where to start a diagnose: what is causing this and if it's
related to mu4e or generally emacs.


Jorge Javier Araya Navarro

unread,
Aug 7, 2025, 1:26:52 PMAug 7
to jman, mu-di...@googlegroups.com
El sábado 02 de agosto del 2025, jman escribió:

> Jorge Javier Araya Navarro <shackra...@gmail.com> writes:
>
>> This is my setup for mu4e:
>> https://gitlab.com/shackra/emacs/-/blob/master/email.el?ref_type=heads
>>
>> Text looks okay on my end. What's your font and what's your
>> mother
>> tongue?
>
> I'm not sure I can answer these questions. What do you mean by
> "font"?
> System font or emacs font? I have a Linux operating system
> completely
> in American English, I use emacs without GUI and no `(setq
> set-face)`
> anywhere. I think I don't have any package installed that could
> be
> related to RTL text.

well, how about both? Check the configuration of your Window
Manager of
choice and see what font it has for Serif, Sans-Serif and
Monospace.

>
> What I probably need is some tips on where to start a diagnose:
> what
> is causing this and if it's related to mu4e or generally emacs.

use `describe-char`/`describe-font` placing the point over the
offending text and see
what it says.

jman

unread,
Aug 8, 2025, 4:37:59 PMAug 8
to Jorge Javier Araya Navarro, mu-di...@googlegroups.com
Jorge Javier Araya Navarro <shackra...@gmail.com> writes:

> use `describe-char`/`describe-font` placing the point over the
> offending text and see
> what it says.

Thank you for the suggestion. I check both and nothing suggests the file being RTL.

But I opened the email with another editor (nano) and it shows the same formatting: I assume it's
some strangeness happening outside Emacs. Since I am no expert and I don't have time to investigate
byte for byte that file further, I'll just give up.

Cheers,

Tim Cross

unread,
Aug 9, 2025, 12:16:20 AMAug 9
to 'jman' via mu-discuss, Jorge Javier Araya Navarro

Just a shot in the dark, but given you indicate the issue occurs in
other mail clients, could it be that the message has an incorrect text
encoding or language header which is confusing clients into thinking the
message is in a right to left language? Emacs supports RtL languages, so
if the message has an incorrect language/encoding header, it is possible
the client will attempt to honour that request.

I would look at the email headers and see if there is anything there
which might be responsible.
Reply all
Reply to author
Forward
0 new messages