From: Kenichi Handa <handa@m17n.org>
To: Sven Joachim <svenjoac@gmx.de>
Cc: cyd@stupidchicken.com, 2317@emacsbugs.donarmstrong.com,
miles.bader@necel.com
Subject: bug#2317: emacs silently ignores buffer file encoding?
Date: Wed, 18 Mar 2009 16:32:37 +0900 [thread overview]
Message-ID: <E1LjqGT-0001bF-PJ@etlken> (raw)
In-Reply-To: <87hc1sy1qk.fsf@turtle.gmx.de> (message from Sven Joachim on Tue, 17 Mar 2009 09:47:47 +0100)
In article <87hc1sy1qk.fsf@turtle.gmx.de>, Sven Joachim <svenjoac@gmx.de> writes:
> On 2009-03-15 17:12 +0100, Chong Yidong wrote:
>>> (1) Start emacs -Q
>>> (2) Visit "/tmp/fff"
>>> (3) Insert the following chars: "θϑΘ"
>>> (4) Set the buffer file encoding to latin1 with: C-x C-m f latin-1 RET
>>> (5) Save the buffer: C-x C-s
>>>
>>> For me, "/tmp/fff" is saved sucessfully, with no error or prompt, using
>>> an encoding of utf-8 -- despite my having explicitly requested latin-1.
> >
> > I think this bug may have been fixed. ISTR seeing the same result when
> > I tested with your recipe a few weeks ago. With latest CVS, however, I
> > get a "Select coding system" prompt. Can you confirm?
> This has been fixed on March 3 by Handa-san, see [1]. However, this fix
> has side effects that I find very annoying: if I visit a file containing
> only ASCII characters and insert non-ASCII characters into the buffer,
> the "Select coding system" prompt pops up as well, although I never
> asked about a specific coding system and would be completely satisfied
> with Emacs silently choosing UTF-8[2] in that case.
Oops, this is surely a bad side effect. I've just fixed it.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-03-18 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 16:12 bug#2317: emacs silently ignores buffer file encoding? Chong Yidong
2009-03-17 8:47 ` Sven Joachim
2009-03-18 7:32 ` Kenichi Handa [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-12 5:25 Miles Bader
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=E1LjqGT-0001bF-PJ@etlken \
--to=handa@m17n.org \
--cc=2317@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=miles.bader@necel.com \
--cc=svenjoac@gmx.de \
/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.