unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Antoine Beaupré" <anarcat@orangeseeds.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: notmuch@notmuchmail.org
Subject: Re: non-ascii email forwarding failures
Date: Tue, 26 Feb 2019 02:51:15 -0500	[thread overview]
Message-ID: <87r2bvgf7w.fsf@curie.anarc.at> (raw)
In-Reply-To: <87mumjnlcq.fsf@fifthhorseman.net>

On 2019-02-26 00:56:53, Daniel Kahn Gillmor wrote:
> On Tue 2019-02-26 00:33:33 -0500, Antoine Beaupré wrote:
>> Message contains characters with unknown encoding.  Really send? (y or n) y
>> Use ASCII as charset? (y or n) y
>
> The right answer in 2019 is to use UTF-8 as a charset, everywhere.  How
> to convince message mode to do that, i don't know.
>
> Presumably your locale is configured as $something.UTF-8 (fr_CA.UTF-8
> perhaps?).

It is.

> Maybe there's some other setting that would also be useful,
> though.  hopefully someone with deeper emacs-fu can weigh in here.

I have no idea. :)

a.

-- 
Non qui parum habet, sed qui plus cupit, pauper est.
It is not the man who has too little, but the man who craves more,
that is poor.            - Lucius Annaeus Seneca (65 AD)

  reply	other threads:[~2019-02-26  7:51 UTC|newest]

Thread overview: 12+ 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
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é [this message]
2019-02-26 10:56           ` David Edmondson
2019-02-26 15:43             ` Antoine Beaupré

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=87r2bvgf7w.fsf@curie.anarc.at \
    --to=anarcat@orangeseeds.org \
    --cc=dkg@fifthhorseman.net \
    --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).