From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Antoine Beaupré" <anarcat@orangeseeds.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [RFC] writing HTML email with notmuch
Date: Mon, 25 Feb 2019 18:15:21 -0500 [thread overview]
Message-ID: <878sy3piie.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87mumjjwv0.fsf@curie.anarc.at>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
On Mon 2019-02-25 18:01:55 -0500, Antoine Beaupré wrote:
> I seem to have forgotten to CC the list in my reply, sorry for the
> noise.
>
> I elided the attachment here because I sent a newer version in
> 87r2bvjx02.fsf@curie.anarc.at.
thanks!
> On 2019-02-25 17:11:26, Antoine Beaupr wrote:
Interesting, your MUA is relying on the default charset=iso-8859-1
(latin-1) or is it charset=iso-8859-15 (latin-7)?
it's sending me octal 0o351 as the last letter of your last name, which
my notmuch-emacs renders as a raw octet ("Beaupr\351"), maybe because
i'm in a UTF-8 locale?
wtf, why are we still failing at this in 2019, with updated MUAs? i
guess it might be my own fault for having this line in my
custom-set-variables in ~/.emacs:
'(message-default-charset (quote utf-8))
but the docs for message-default-charset say:
This variable is obsolete since 26.1;
The default charset comes from the language environment
shouldn't emacs mml mode explicitly mark the charset in the Content-Type
header when generating a text/plain part no matter what?
grumpily,
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-02-25 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 1:52 [RFC] writing HTML email with notmuch Antoine Beaupré
2019-02-25 18:22 ` Istvan Marko
2019-02-25 18:56 ` Brian Sniffen
2019-02-25 22:58 ` Antoine Beaupré
2019-02-25 21:18 ` Daniel Kahn Gillmor
[not found] ` <87lg23ldrl.fsf@curie.anarc.at>
2019-02-25 23:01 ` Antoine Beaupré
2019-02-25 23:15 ` Daniel Kahn Gillmor [this message]
2019-02-26 5:33 ` non-ascii email forwarding failures Antoine Beaupré
2019-02-26 5:56 ` Daniel Kahn Gillmor
2019-02-26 7:51 ` Antoine Beaupré
2019-02-26 10:56 ` David Edmondson
2019-02-26 15:43 ` Antoine Beaupré
[not found] <mailman.1.1551124801.2659.notmuch@notmuchmail.org>
2019-02-28 7:23 ` [RFC] writing HTML email with notmuch Jayanth R Varma
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=878sy3piie.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=anarcat@orangeseeds.org \
--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).