From: Pascal J.Bourguignon <pjb@informatimago.com>
Cc: clisp-list@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: emacs refuses to save file in the same encoding it was read
Date: Tue, 14 Oct 2003 05:42:12 +0200 [thread overview]
Message-ID: <16267.28820.604849.881886@thalassa.informatimago.com> (raw)
In-Reply-To: <200310140052.JAA23914@etlken.m17n.org>
Kenichi Handa writes:
> In article <uekxk97pv.fsf@gnu.org>, Sam Steingold <sds@gnu.org> writes:
> > I have a file which starts with this line:
> > ;;; -*- coding: utf-8-unix -*-
>
> > it is opened and displayed by emacs correctly.
> > however, when I try to modify and save it, I get the following question:
>
> > Selected encoding mule-utf-8-unix disagrees with iso-2022-7bit specified
> > by file contents. Really save (else edit coding cookies and try again)?
> > (y or n)
>
> > when I answer affirmatively, the file is saved, but a line
> > ;; -*- coding: iso-2022-7bit; -*-
> > is added in front of my cookie.
>
> > what is going on?
>
> I can't reproduce this bug. Could you please send me the
> file that causes this problem in 8-bit safe way (base64 or
> uuencode)?
I had recently a similar problem (without a -*- coding: -*-
line). I've got an answer on usenet saying that emacs did not support
yet fully unicode, so when you have japanese characters, you must save
in iso-2022.
--
__Pascal_Bourguignon__
http://www.informatimago.com/
Do not adjust your mind, there is a fault in reality.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
next prev parent reply other threads:[~2003-10-14 3:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 20:08 emacs refuses to save file in the same encoding it was read Sam Steingold
2003-10-14 0:52 ` Kenichi Handa
2003-10-14 3:42 ` Pascal J.Bourguignon [this message]
2003-10-22 9:14 ` Juri Linkov
2003-10-22 12:43 ` Stefan Monnier
2003-10-22 15:17 ` Juri Linkov
2003-10-22 17:15 ` Stefan Monnier
2003-10-23 18:38 ` Richard Stallman
2003-10-23 19:15 ` Stefan Monnier
2003-10-24 10:42 ` Richard Stallman
2003-10-24 14:14 ` Stefan Monnier
2003-10-25 22:26 ` Richard Stallman
2003-10-26 18:52 ` Stefan Monnier
2003-10-23 19:27 ` Alan Shutko
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=16267.28820.604849.881886@thalassa.informatimago.com \
--to=pjb@informatimago.com \
--cc=clisp-list@lists.sourceforge.net \
--cc=emacs-devel@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).