all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Per Starbäck" <per@starback.se>
Cc: emacs-devel@gnu.org
Subject: Re: Why ("/#[^/]+#\\'" . emacs-mule) ?
Date: Mon, 25 Mar 2013 16:13:35 +0200	[thread overview]
Message-ID: <83sj3j1sa8.fsf@gnu.org> (raw)
In-Reply-To: <CADkQgvvLa8Y21i8EyjvPSq=6HPgQT6+OPG3=XxWEeS+0EcXHzA@mail.gmail.com>

> Date: Mon, 25 Mar 2013 14:08:36 +0100
> From: Per Starbäck <per@starback.se>
> 
> Why are #autosave# files opened with the emacs-mule coding?

They are not, not in latest versions of Emacs.

> I don't use recover-file a lot. When I have to use autosave files I
> usually open them up in their own buffers and compare and copy
> "manually".
> Very often when I open them I have to immediately use
> revert-buffer-with-coding-system because they are utf8 files.

Strange that you need that.  When I do "M-x recover-this-file RET", I
get a buffer in utf-8-emacs-unix, which is what I expect.

> For a long time I have wished that the coding of those files would be
> recognised like for other files. I thought of reporting this as a bug,
> but since
> auto-coding-list (in lisp/international/mule.el) has an explicit line
> 
>     ("/#[^/]+#\\'" . emacs-mule)))
> 
> it's evidently on purpose, so instead I will ask here. What is that purpose?

The purpose is back-compatibility with auto-save files from prior
versions.  But recover-file overrides this and uses auto-save-coding,
so I'm unsure why the above matters in your case.




  parent reply	other threads:[~2013-03-25 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 13:08 Why ("/#[^/]+#\\'" . emacs-mule) ? Per Starbäck
2013-03-25 13:21 ` Andreas Schwab
2013-03-25 13:59   ` Eli Zaretskii
2013-03-25 14:13 ` Eli Zaretskii [this message]
2013-03-25 14:50   ` Andreas Schwab
2013-03-26 15:57   ` [SPG,spf=20]Re: " Per Starbäck

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83sj3j1sa8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=per@starback.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.