From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Defaults for elisp-mode files
Date: Thu, 04 Oct 2012 15:01:06 +0900 [thread overview]
Message-ID: <874nmalqsd.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <jwv7gr6aojw.fsf-monnier+emacs@gnu.org>
Stefan Monnier writes:
> No, I mean to set auto-coding-list so that .el files get read as utf-8.
I was afraid you meant that, but one can always hope. ;-)
> I don't think so: if the file doesn't have a `coding:' cookie but has
> significant non-ASCII chars in it, we usually sooner or later get bug
> reports about it (because someone loaded the file in an locale where
> the encoding ended up not recognized correctly).
Funny, that's another bug that just doesn't show up on XEmacs channels
that I know of. The reason is simple: ISO-2022-JP is unambiguous and
very reliably detectable.[1]
Very occasionally somebody will ask for help with a 3rd party file. I
explain about coding cookies and C-u C-x C-f ... C-x C-m f iso-2022-jp
and never hear from them about that again.
Of course, all of the above would be true of UTF-8.
> > While you *can* set `auto-coding-alist', I think it will cause a lot
> > of pain.
>
> We'll see ;-)
You were warned. ;-)
Footnotes:
[1] At least in my experience.
next prev parent reply other threads:[~2012-10-04 6:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 18:06 Defaults for elisp-mode files Stefan Monnier
2012-10-03 18:22 ` Drew Adams
2012-10-03 18:41 ` Christopher Schmidt
2012-10-04 0:59 ` Juanma Barranquero
2012-10-04 1:29 ` Stephen J. Turnbull
2012-10-04 3:48 ` Stefan Monnier
2012-10-04 3:56 ` Christopher Monsanto
2012-10-04 14:15 ` Juanma Barranquero
2012-10-04 15:37 ` Christopher Monsanto
2012-10-04 16:24 ` Juanma Barranquero
2012-10-04 17:00 ` Andreas Schwab
2012-10-04 17:12 ` Juanma Barranquero
2012-10-04 17:07 ` Stephen J. Turnbull
2012-10-04 6:01 ` Stephen J. Turnbull [this message]
2012-10-04 19:10 ` Andreas Röhler
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=874nmalqsd.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.