-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"# coding: utf-8" line when replying #32
Comments
Hi, First of all I don't use Regards, |
That's the html of the message I was replying to (just some text): <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!-- 2020-02-28 Fri 16:35 --><meta http-equiv="Content-Type" content="text/html;charset=utf-8"/><meta name="viewport" content="width=device-width, initial-scale=1"/><meta name="generator" content="Org mode"/><meta name="author" content="wedens"/></head><body>
<div style="font-family:"Arial";font-size:10pt;line-height:11pt;" id="content">
<p style="text-decoration:none;margin-bottom:0px;margin-top:10px;line-height:11pt;font-size:10pt;font-family:"Arial";max-width:100ch;">
test123<br/></p>
</div>
</body></html> Also, when I try to reply to it, emacs prompts me to select coding system and there are two buffers (other than message itself) open: first buffer:
second buffer:
Seems like something weird is goning on here: |
I tried to reproduce this issue but I could not. Could you disable your Emacs configuration and try again ? |
Any update ? |
No, sorry. I'm still unsure why it happens. |
I use org-msg with mu4e (1.2.0) and emacs 27.
When I reply to a message,
# coding: utf-8
gets added at the end of the message. It's not present when I type the reply, so it's added by some hook. When I doorg-msg-preview
on the reply, this line is also added after the reply text.html of the reply:
Is there some way to avoid this line being added?
org-msg related configuration:
PS: I'm not sure if it's related to org-msg and if it's not, I'll be glad for any pointers to where to look next.
The text was updated successfully, but these errors were encountered: