From: Eli Zaretskii <eliz@gnu.org>
To: charles@aurox.ch (Charles A. Roelli)
Cc: 28266@debbugs.gnu.org
Subject: bug#28266: 25.2; RMAIL FCC coding issue
Date: Fri, 22 Sep 2017 23:08:13 +0300 [thread overview]
Message-ID: <83y3p6bioi.fsf@gnu.org> (raw)
In-Reply-To: <m21smymvbi.fsf@aurox.ch> (charles@aurox.ch)
> Date: Fri, 22 Sep 2017 20:39:45 +0200
> From: charles@aurox.ch (Charles A. Roelli)
> CC: 28266@debbugs.gnu.org
>
> > Date: Fri, 22 Sep 2017 16:13:58 +0300
> > From: Eli Zaretskii <eliz@gnu.org>
> >
> > I cannot reproduce this with the current emacs-26 branch tip.
> > However, in my case, Emacs asked for a suitable coding-system each
> > time I wanted to send a message. Answering UTF-8 produced a valid
> > encoding in both cases.
> >
> > So perhaps the difference, and the reason for a problem you see, is
> > the default encoding in your case, which you didn't show. (In my
> > case, the default is Latin-1.)
>
> Hmm, I was never queried for a coding system.
Because your default is UTF-8. This is normal.
> I've repeated the issue on GNU/Linux with 25.3 and macOS with 25.3
> and emacs-26. And I don't set any special locales/language
> environments:
>
> > Important settings:
> > value of $LANG: en_GB.UTF-8
> > locale-coding-system: utf-8-unix
With en_US.UTF-8 on GNU/Linux, using the current emacs-26 branch, I
see no problem: both messages are sent with a correct encoding.
What happens if you don't visit the FCC file after the first message
is sent, only after the second? Do you still see the second message
encoded incorrectly?
next prev parent reply other threads:[~2017-09-22 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 18:59 bug#28266: 25.2; RMAIL FCC coding issue Charles A. Roelli
2017-09-22 13:13 ` Eli Zaretskii
2017-09-22 18:39 ` Charles A. Roelli
2017-09-22 20:08 ` Eli Zaretskii [this message]
2017-09-24 8:47 ` Charles A. Roelli
2017-09-24 12:03 ` Alexis
2022-01-23 15:54 ` Lars Ingebrigtsen
2022-02-20 19:30 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y3p6bioi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28266@debbugs.gnu.org \
--cc=charles@aurox.ch \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.