emacs refuses to save file in the same encoding it was read

emacs refuses to save file in the same encoding it was read

[Sam Steingold]

GNU Emacs 21.3.50.1 (i386-msvc-nt5.0.2195)
 of 2003-10-08 on WINSTEINGOLDLAP
--with-msvc (12.00)

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?

My understanding is that since everything can be encoded with utf-8,
there is no reason for Emacs to suggest a different encoding.
I seem to remember that there are some identical characters - from the
unicode POV - which Emacs represents differently.
First, I thought this bug has been fixed already.
Second, I thought it was irrelevant here anyway: the file is read in
utf-8!

It appears that buffer-file-coding-system is somehow set to
iso-2022-7bit; I sets default value to utf-8.

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
main(a){printf(a,34,a="main(a){printf(a,34,a=%c%s%c,34);}",34);}

Re: emacs refuses to save file in the same encoding it was read

[Kenichi Handa]

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)?

---
Ken'ichi HANDA
handa@m17n.org

Re: emacs refuses to save file in the same encoding it was read

[Pascal J.Bourguignon]

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

Re: emacs refuses to save file in the same encoding it was read

[Juri Linkov]

Sam Steingold <sds@gnu.org> writes:
> 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?

This line is added by the function `bbdb-write-file-hook-fn'.
Up to now it was added to `local-write-file-hooks' locally only in
the bbdb buffer.  But now the value of `local-write-file-hooks'
is set by the function `add-hook' globally, so this hook adds
this line in the beginning of every saved buffer.

-- 
http://www.jurta.org/emacs/

Re: emacs refuses to save file in the same encoding it was read

[Stefan Monnier]

>> 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?

> This line is added by the function `bbdb-write-file-hook-fn'.
> Up to now it was added to `local-write-file-hooks' locally only in
> the bbdb buffer.  But now the value of `local-write-file-hooks'
> is set by the function `add-hook' globally, so this hook adds
> this line in the beginning of every saved buffer.

Since when dos it do that and why ?


        Stefan


PS: If the hook should be modified locally, you should set the `local'
    argument to a non-nil value.

Re: emacs refuses to save file in the same encoding it was read

[Juri Linkov]

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> > This line is added by the function `bbdb-write-file-hook-fn'.
> > Up to now it was added to `local-write-file-hooks' locally only in
> > the bbdb buffer.  But now the value of `local-write-file-hooks'
> > is set by the function `add-hook' globally, so this hook adds
> > this line in the beginning of every saved buffer.
> 
> Since when does it do that and why ?

I encountered this bug yesterday after I updated Emacs from CVS.

> PS: If the hook should be modified locally, you should set the `local'
>     argument to a non-nil value.

It's not easy to fix, because bbdb is not part of Emacs.

-- 
http://www.jurta.org/emacs/

Re: emacs refuses to save file in the same encoding it was read

[Stefan Monnier]

>> PS: If the hook should be modified locally, you should set the `local'
>> argument to a non-nil value.
> It's not easy to fix, because bbdb is not part of Emacs.

Emacs should be fixed to maintain the backward compatibility, of course.
But a bug-report to bbdb-list is in order, I think.


        Stefan

Re: emacs refuses to save file in the same encoding it was read

[Richard Stallman]

    This line is added by the function `bbdb-write-file-hook-fn'.
    Up to now it was added to `local-write-file-hooks' locally only in
    the bbdb buffer.  But now the value of `local-write-file-hooks'
    is set by the function `add-hook' globally, so this hook adds
    this line in the beginning of every saved buffer.

it looks like my change in add-hook is not right for
variables that become local when set.

dies ths chg work in general?

*** subr.el.~1.365.~	Mon Oct 20 19:26:00 2003
--- subr.el	Thu Oct 23 06:10:42 2003
***************
*** 852,857 ****
--- 852,859 ----
  function, it is changed to a list of functions."
    (or (boundp hook) (set hook nil))
    (or (default-boundp hook) (set-default hook nil))
+   (if (local-variable-if-set-p hook)
+       (setq local t))
    (if local (unless (local-variable-if-set-p hook)
  	      (set (make-local-variable hook) (list t)))
      ;; Detect the case where make-local-variable was used on a hook

Re: emacs refuses to save file in the same encoding it was read

[Stefan Monnier]

>     This line is added by the function `bbdb-write-file-hook-fn'.
>     Up to now it was added to `local-write-file-hooks' locally only in
>     the bbdb buffer.  But now the value of `local-write-file-hooks'
>     is set by the function `add-hook' globally, so this hook adds
>     this line in the beginning of every saved buffer.

> it looks like my change in add-hook is not right for
> variables that become local when set.

> dies ths chg work in general?

I think the code is already pretty messy, so I'd rather avoid adding
yet-another-test.  Could you explain the reason for the recent change
that introduced the new problem?  Maybe we can fix it in some other way?


        Stefan

Re: emacs refuses to save file in the same encoding it was read

[Alan Shutko]

Richard Stallman <rms@gnu.org> writes:

> it looks like my change in add-hook is not right for
> variables that become local when set.
>
> dies ths chg work in general?

It fixes the problems I was seeing.

-- 
Alan Shutko <ats@acm.org> - I am the rocks.
3 days, 20 hours, 33 minutes, 22 seconds till closing!
The only substitute for good manners is *faster* reflexes. ;^)

Re: emacs refuses to save file in the same encoding it was read

[Richard Stallman]

    I think the code is already pretty messy, so I'd rather avoid adding
    yet-another-test.  Could you explain the reason for the recent change
    that introduced the new problem?  Maybe we can fix it in some other way?

sorry, i don't remember, but i think i saw a bug in some case.

does my fix work?

Re: emacs refuses to save file in the same encoding it was read

[Stefan Monnier]

>     I think the code is already pretty messy, so I'd rather avoid adding
>     yet-another-test.  Could you explain the reason for the recent change
>     that introduced the new problem?  Maybe we can fix it in some other way?
> sorry, i don't remember, but i think i saw a bug in some case.

It would be helpful if you could remember.  I can't think of any case where
the old code could be wrong.  The logic is as follows:

    If t is not a member of (symbol-value hook), then use
    `setq' rather than `setq-default' to modify the value.

There's no need to distinguish between the case where the variable is
buffer-local or not: if it is local-variable-if-set-p then the code
does the same as the new code and if it is not, `setq' and `setq-default'
do the same anyway.

> does my fix work?

It does, but I'd rather remove the recent patch which does not fix anthing
as far as I can tell.  Or at least I'd rather fix it by replacing
`local-variable-p' by `local-variable-if-set-p' in your recent patch.

The fact that you did not notice the bug even after I pointed out the
faulty code shows that the logic of the code is already complex enough
and should not be made worse as your two patches do.


        Stefan

Re: emacs refuses to save file in the same encoding it was read

[Richard Stallman]

i found it easier to rewrite the code than to understand the old code.

due to the broken arm, i can't discuss it further.

Re: emacs refuses to save file in the same encoding it was read

[Stefan Monnier]

> i found it easier to rewrite the code than to understand the old code.

You didn't need to understand the old code: I wrote it, I understand it,
I would have explained it and/or fixed it.

Also, I'm afraid there is a misunderstanding:
I was talking about the change to add-hook (not to remove-hook), but
this change is a two-line patch: very much unlike a rewrite.


        Stefan