From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: auto-save-visited-file-name
Date: 16 Oct 2003 21:52:34 +0200 [thread overview]
Message-ID: <m3he2955a5.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <jwvad81xgeb.fsf-monnier+emacs/devel@vor.iro.umontreal.ca>
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> > .. but doesn't that mean that auto-save files are always saved
> > in emacs-mule rather than the current coding of the buffer?
> > That sounds like a more generic error that needs fixing anyway.
>
> No, I think it's a very reasonable choice (and I know it's been discussed
> here and more recently on XEmacs's lists).
> This is the only encoding that we know for sure will not lose any
> information, will succeed without needing to prompt the user for more
> details, and it is also more efficient which I still consider relevant in
> the context of auto-saving. It's not perfect, but the other options aren't
> much more attractive.
Well, we could use the buffer's coding if it suffices -- and only revert
to emacs-mule if it doesn't. That would not require any prompting...
I assume that the original buffer's coding is used if the
auto-save file is restored.
But I have no strong opinions, so let's not discuss it further.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2003-10-16 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 18:59 auto-save-visited-file-name Stefan Monnier
2003-10-15 21:20 ` auto-save-visited-file-name Kim F. Storm
2003-10-16 17:10 ` auto-save-visited-file-name Stefan Monnier
2003-10-16 19:52 ` Kim F. Storm [this message]
2003-10-16 7:19 ` auto-save-visited-file-name Eli Zaretskii
2003-10-17 20:46 ` auto-save-visited-file-name Richard Stallman
2003-10-17 21:14 ` auto-save-visited-file-name Stefan Monnier
2003-10-23 15:55 ` auto-save-visited-file-name Kevin Rodgers
2003-10-24 5:16 ` auto-save-visited-file-name Richard Stallman
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=m3he2955a5.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@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).