From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: problem with editing/decoding utf-8 text
Date: Fri, 30 May 2003 15:24:29 +0200 [thread overview]
Message-ID: <84smqw4lf6.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: mailman.7046.1054298932.21513.help-gnu-emacs@gnu.org
Fery <engard.ferenc@innomed.hu> writes:
>> You said that Emacs corrupted your files in some cases. Could you
>> please tell the exact steps to reproduce this with the file you sent?
>
> $ emacs test
>
> - type 'a' and then backspace
> - ^X^S
> - ^G
> - ^X^C
> - n
> - yes
>
> After that, 'test' is disappeared, and '#test#' contains a different
> file compared to the old test.
The autosave files (#test# is an autosave file) are saved in the
emacs-mule encoding, because we're sure that this encoding can
represent all characters that Emacs can represent. Using any other
encoding (including UTF-8) may possibly lead to information loss. At
least, it might have to ask the user, and you surely don't want
auto-saving to ask the user.
--
This line is not blank.
next prev parent reply other threads:[~2003-05-30 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6818.1054022957.21513.help-gnu-emacs@gnu.org>
2003-05-27 11:10 ` problem with editing/decoding utf-8 text Oliver Scholz
[not found] ` <3ED37785.CA5A9AD5@innomed.hu>
[not found] ` <ubrxnb5m2.fsf@ID-87814.user.dfncis.de>
2003-05-30 12:45 ` Fery
[not found] ` <mailman.7046.1054298932.21513.help-gnu-emacs@gnu.org>
2003-05-30 13:24 ` Kai Großjohann [this message]
[not found] <mailman.6770.1053942670.21513.help-gnu-emacs@gnu.org>
2003-05-27 11:05 ` Oliver Scholz
2003-05-27 11:41 ` Oliver Scholz
2003-05-27 8:06 Fery
-- strict thread matches above, loose matches on Subject: below --
2003-05-26 9:47 Fery
2003-05-26 9:47 Fery
[not found] <mailman.6635.1053692285.21513.help-gnu-emacs@gnu.org>
2003-05-23 16:50 ` Kai Großjohann
2003-05-23 19:23 ` Oliver Scholz
2003-05-23 20:53 ` Kai Großjohann
2003-05-23 21:20 ` Stefan Monnier
2003-05-23 12:08 Fery
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=84smqw4lf6.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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.
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).