[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: edited file is deleted when the file cannot be saved because of its
Re: edited file is deleted when the file cannot be saved because of its coding system
Fri, 6 Jun 2003 21:31:11 +0900 (JST)
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.2.92 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI)
In article <address@hidden>, "Eli Zaretskii" <address@hidden> writes:
>> > Select one of the following safe coding systems: >
>> utf-8 mule-utf-16-le mule-utf-16-be raw-text emacs-mule >
>> > ---------------
>> > After that, I have entered C-g to escape from this
>> function. > At this point, my original file has gone
>> (and, there is no > recovery file yet).
>> I can't reproduce it. The original file still exists
>> after I type C-g at the above point.
> Wasn't this a bug in some v21.x of Emacs that was fixed
> later? Handa-san, did you try this in the CVS version of
Oops, from some point, the mails between me and Fery don't
include address@hidden in CC:.
I'll attach the last mail I sent to him. It seems that the
problem is already fixed in HEAD.
Date: Fri, 6 Jun 2003 14:22:07 +0900 (JST)
From: Kenichi Handa <address@hidden>
In-reply-to: <address@hidden> (message from Fery on Thu, 05 Jun 2003 13:17:53
Subject: Re: edited file is deleted when the file cannot be saved because of
its coding system
In article <address@hidden>, Fery <address@hidden> writes:
> I have played a bit more with this problem, and noticed
> that it saves a backup with a ~ on the end, so I have the
> original file! Sorry, I have missed this. So, if I have
> 'test', after ^X^S I will have 'test~' (it is moved,
> timestamp etc. is retained), and after quitting '#test#'
> (with internal encoding) and 'test~' with the original
I confirmed that hahaviour with 21.3 and CVS RC branch.
And I found that this problem is now fixed in HEAD branch.
In HEAD, at the point of Emacs asking you a
coding system, 'test' is surely moved to 'test~', but when
you type C-g, 'test~' is moved back to 'test'.
>> In C locale, iso-latin-1 has higher priority than utf-8,
>> and all bytes in your file are regarded as valid for
>> iso-latin-1. (The byte \225 (#x95) is also registered as
>> valid latin code in latin-extra-code-table).
> After all, emacs do not permit to save it, so from this
> point of view it is not a valid iso-latin-1 file for
> emacs. :-O
Sorry, what I wrote was wrong. In 21.3 and RC, \225 is not
yet registered as a valid latin code, but has a bug in code
detection routine. This bug is already fixed in the HEAD