unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22436@debbugs.gnu.org
Subject: bug#22436: read-coding-system uses wrong default when called from write-file
Date: Sat, 23 Jan 2016 09:45:39 +0000	[thread overview]
Message-ID: <CAPM58ojw5VxXFrTnBAW4MwBAPGEP8TmC1aX7jTrc7DODFnDLsA@mail.gmail.com> (raw)
In-Reply-To: <83vb6k6dqi.fsf@gnu.org>

On 23 January 2016 at 05:56, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Richard Copley <rcopley@gmail.com>
>> Date: Fri, 22 Jan 2016 23:23:40 +0000
>> Cc: 22436@debbugs.gnu.org
>>
>> On 22 January 2016 at 21:23, Eli Zaretskii <eliz@gnu.org> wrote:
>> >> From: Richard Copley <rcopley@gmail.com>
>> >> Date: Fri, 22 Jan 2016 19:31:07 +0000
>> >>
>> >> >From "emacs -Q", enter a ‘ in the scratch buffer (e.g., by typing "C-x
>> >> 8 ["). Save or write the buffer. The minibuffer prompts "Select coding
>> >> system (default chinese-iso-8bit): ".
>> >
>> > Why do you think that's wrong?
>>
>> Of course it's wrong. What do you mean?
>
> Wrong how? in what way? what did you expect to happen instead?

Wrong in the ordinary sense of the word, in that it is not right.
It is however exactly what I expected.

> Your locale's default encoding, cp1252, cannot encode this character,
> so Emacs asked you to provide an encoding that can, and offered
> chinese-iso-8bit as the default.

Yes.

> An encoding can be considered "wrong" if it fails to encode a
> character.  AFAICS, chinese-iso-8bit does succeed in encoding it, so
> the above definition of "wrong" doesn't fit.

It encodes the character to #xa1 #xae . When I open the file that is
decoded as "¡®", without asking any questions. Isn't that what you
saw? Are you going to tell me that's right too?

> In addition, there should be a *Warning* buffer displayed where you
> have a long list of encodings Emacs knows about that can encode this
> character; chinese-iso-8bit is just one of them, but the text there
> tells you to select any one of them.  Do you see that buffer
> displayed?

Yes, but chinese-iso-8bit is not on the list.

> Given all this information, please do tell why you think what Emacs
> did was wrong,

Do you seriously think it's the right thing to do? That's the last thing
I expected. I don't know how to respond.

> and what did you think Emacs should have done instead.

I think Emacs should pick something less surprising and unhelpful,
like utf-8.





  reply	other threads:[~2016-01-23  9:45 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPM58ojw5VxXFrTnBAW4MwBAPGEP8TmC1aX7jTrc7DODFnDLsA@mail.gmail.com \
    --to=rcopley@gmail.com \
    --cc=22436@debbugs.gnu.org \
    --cc=eliz@gnu.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://git.savannah.gnu.org/cgit/emacs.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).