unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Michael Kifer <kifer@cs.sunysb.edu>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: lisp/ChangeLog coding system
Date: Mon, 29 Apr 2002 16:33:16 +0300 (IDT)	[thread overview]
Message-ID: <Pine.SUN.3.91.1020429162751.27060A-100000@is> (raw)
In-Reply-To: <86sn5ehhr1.fsf@gerd.dnsq.org>


On 29 Apr 2002, Gerd Moellmann wrote:

> Eli Zaretskii <eliz@is.elta.co.il> 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.

  reply	other threads:[~2002-04-29 13:33 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 14:45 lisp/ChangeLog coding system Gerd Moellmann
2002-04-27 22:41 ` Richard Stallman
2002-04-27 23:05   ` Michael Kifer
2002-04-29  5:01     ` Eli Zaretskii
2002-04-29 11:22       ` Gerd Moellmann
2002-04-29 13:33         ` Eli Zaretskii [this message]
2002-04-30  5:18           ` Richard Stallman
2002-04-30  5:31             ` Eli Zaretskii
2002-05-01  7:13               ` Richard Stallman
2002-05-01 11:56                 ` Eli Zaretskii
2002-04-29  5:06     ` Richard Stallman
2002-04-29  6:10       ` Michael Kifer
2002-04-29 10:00         ` Eli Zaretskii
2002-04-30  5:18           ` Richard Stallman
2002-04-30  5:19         ` Richard Stallman
2002-04-30  5:22           ` Michael Kifer
2002-04-30  5:32             ` Eli Zaretskii
2002-04-30  5:53               ` Michael Kifer
2002-04-30  9:19                 ` Eli Zaretskii
2002-04-30 15:35                   ` Michael Kifer
2002-04-28  3:06   ` Karl Eichwalder
2002-04-28 18:22     ` Eli Zaretskii
2002-04-28 23:19       ` Stefan Monnier
2002-04-29  5:03         ` Eli Zaretskii
2002-04-29 18:39         ` Richard Stallman
2002-04-29  1:10       ` Stephen J. Turnbull
2002-04-29  1:55         ` Stefan Monnier
2002-04-29  5:07           ` Eli Zaretskii
2002-04-29 11:28           ` Stephen J. Turnbull
2002-04-29 11:49             ` Miles Bader
2002-04-29 13:31             ` Stefan Monnier
2002-04-29 15:54               ` Stephen J. Turnbull
2002-04-29 15:56               ` Karl Eichwalder
2002-04-29 16:38               ` Miles Bader
2002-04-29 13:43             ` Eli Zaretskii
2002-04-29  5:05     ` Richard Stallman
2002-04-29 15:52       ` Karl Eichwalder
2002-04-29 16:37         ` Stefan Monnier
2002-04-29 18:43           ` Eli Zaretskii
2002-04-29 18:41         ` Eli Zaretskii
2002-04-29 19:12           ` Simon Josefsson
2002-04-30  4:35             ` Eli Zaretskii
2002-04-30  8:50               ` Simon Josefsson
2002-04-30  5:19         ` Richard Stallman
2002-04-30 18:09           ` Karl Eichwalder

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=Pine.SUN.3.91.1020429162751.27060A-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=kifer@cs.sunysb.edu \
    --cc=rms@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).