From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: rcopley@gmail.com, 22436@debbugs.gnu.org
Subject: bug#22436: read-coding-system uses wrong default when called from write-file
Date: Sat, 23 Jan 2016 16:39:14 +0200 [thread overview]
Message-ID: <83zivw4ay5.fsf@gnu.org> (raw)
In-Reply-To: <m37fj01jtl.fsf@gnus.org> (message from Lars Magne Ingebrigtsen on Sat, 23 Jan 2016 14:55:50 +0100)
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Cc: rcopley@gmail.com, 22436@debbugs.gnu.org
> Date: Sat, 23 Jan 2016 14:55:50 +0100
>
> >> Could the default be improved upon?
> >
> > We can sort the list differently. But if all we want is to always get
> > UTF-8 at the head, there's a much easier way, see my other message
> > where I mentioned prefer-coding-system.
>
> I guess I'm just saying that I think the least surprising default coding
> system here would be utf-8.
For you, maybe. What about all those Chinese out there? What if I'm
writing an email to someone in China? Etc., etc.
> That is, Emacs should say utf-8 unless the user has called
> `prefer-coding-system' with something else.
Most people who care about that already have their locales use UTF-8.
So the problem largely doesn't exist. It's not an accident that this
was reported by a Windows user.
Anyway, this stuff worked for years, why should we suddenly change?
next prev parent reply other threads:[~2016-01-23 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 19:31 bug#22436: read-coding-system uses wrong default when called from write-file Richard Copley
2016-01-22 21:23 ` Eli Zaretskii
2016-01-22 23:23 ` Richard Copley
2016-01-23 5:56 ` Eli Zaretskii
2016-01-23 9:45 ` Richard Copley
2016-01-23 11:31 ` Eli Zaretskii
2016-01-23 11:53 ` Richard Copley
2016-01-23 13:09 ` Eli Zaretskii
2016-01-23 13:12 ` Lars Magne Ingebrigtsen
2016-01-23 13:46 ` Eli Zaretskii
2016-01-23 13:55 ` Lars Magne Ingebrigtsen
2016-01-23 14:39 ` Eli Zaretskii [this message]
2016-01-25 22:38 ` Richard Copley
2016-01-26 15:39 ` Eli Zaretskii
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=83zivw4ay5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22436@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rcopley@gmail.com \
/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.