From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: encoding used by those #some.txt# backup?
Date: Mon, 19 Jan 2009 22:37:44 +0200 [thread overview]
Message-ID: <usknfuj53.fsf@gnu.org> (raw)
In-Reply-To: <692dfade-ef63-40aa-96e9-229d65e1a584@r41g2000prr.googlegroups.com>
> From: Xah Lee <xahlee@gmail.com>
> Date: Mon, 19 Jan 2009 10:30:34 -0800 (PST)
>
> it seems emacs's crash backup files saved my utf-8 files in a
> different encoding.
It's the internal representation of characters used by Emacs. Since
auto-save files must be always encoded correctly, the only safe way of
doing that is to dump the internal representation.
> If i have a crash, then opening the #x.txt# file the content is:
>
> \234\364\370\261 something
>
> since my files have lots of unicode, this renders those auto-save not
> usable.
M-x recover-file RET should DTRT.
> is this a bug or am i missing some file encoding for this type of
> backups?
M-x recover-file RET should decode them correctly.
next prev parent reply other threads:[~2009-01-19 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 18:30 encoding used by those #some.txt# backup? Xah Lee
2009-01-19 20:37 ` Eli Zaretskii [this message]
2009-01-29 5:59 ` fnn
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=usknfuj53.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).