[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lisp/ChangeLog coding system
From: |
Eli Zaretskii |
Subject: |
Re: lisp/ChangeLog coding system |
Date: |
Mon, 29 Apr 2002 16:33:16 +0300 (IDT) |
On 29 Apr 2002, Gerd Moellmann wrote:
> Eli Zaretskii <address@hidden> writes:
>
> > Gerd, can you tell what exactly was wrong with the ChageLog before you
> > fixed it?
>
> Inserting a new change log entry and trying to save the file lead to
> the ``choose coding system'' dialog.
>
> The value of buffer-file-coding-system was iso-2022-7bit, and
> find-charset-region on the whole buffer returned `(ascii
> eight-bit-graphic)', I think.
>
> The change in question is the one from version 1.3763 to 1.3764.
Thanks for the info. As far as I could see, version 1.3764 is encoded in
Latin-1, not iso-2022-7bit. But since there's a ``coding: iso-2022-7bit''
cookie there, buffer-file-coding-system gets set to iso-2022-7bit, and
Emacs then pops the select-safe-coding-system dialog when you try to save.
The question is how did the file get saved on Michael's machine as
Latin-1. Ideas, anyone?
I think we should change save-buffer to pay attention to the coding:
cookie. This was discussed long ago (more than a year, IIRC), but never
got coded. It's a bad mantra, IMHO, that Emacs produces a file whose
coding: lies through its teeth.
- lisp/ChangeLog coding system, Gerd Moellmann, 2002/04/26
- Re: lisp/ChangeLog coding system, Richard Stallman, 2002/04/29
- Re: lisp/ChangeLog coding system, Michael Kifer, 2002/04/29
- Re: lisp/ChangeLog coding system, Eli Zaretskii, 2002/04/29
- Re: lisp/ChangeLog coding system, Richard Stallman, 2002/04/30
- Re: lisp/ChangeLog coding system, Richard Stallman, 2002/04/30
- Re: lisp/ChangeLog coding system, Michael Kifer, 2002/04/30
- Re: lisp/ChangeLog coding system, Eli Zaretskii, 2002/04/30
- Re: lisp/ChangeLog coding system, Michael Kifer, 2002/04/30