From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: bug-gnu-emacs@gnu.org
Subject: bug#8308: 23.3; Use utf-8 for writing abbrev file
Date: Mon, 21 Mar 2011 19:24:16 +0100 [thread overview]
Message-ID: <4D8797D0.3010109@easy-emacs.de> (raw)
In-Reply-To: <jwvlj081qgo.fsf-monnier+emacs@gnu.org>
Am 21.03.2011 15:50, schrieb Stefan Monnier:
>> Is it OK to change the encoding for abbrev file to utf-8?
>> === modified file 'lisp/abbrev.el'
>> --- a/lisp/abbrev.el 2011-03-21 05:49:12 +0000
>> +++ b/lisp/abbrev.el 2011-03-21 06:20:36 +0000
>> @@ -225,9 +225,9 @@
>> abbrev-file-name)))
>> (or (and file (> (length file) 0))
>> (setq file abbrev-file-name))
>> - (let ((coding-system-for-write 'emacs-mule))
>> + (let ((coding-system-for-write 'utf-8))
>> (with-temp-file file
>> - (insert ";;-*-coding: emacs-mule;-*-\n")
>> + (insert ";;-*-coding: utf-8;-*-\n")
>> (dolist (table
>> ;; We sort the table in order to ease the automatic
>> ;; merging of different versions of the user's abbrevs
>
> Sounds good in general, but I'm wondering whether we should worry about
> the presence of abbrevs which include bytes (aka eight-bit-chars).
> Using `utf-8-emacs' should fix those issues, but would then bump into
> the problem that such abbrev files wouldn't be compatible with Emacs-22.
>
>
> Stefan
>
Hi,
so maybe not hard-code it, rather have a variable?
Andreas
next prev parent reply other threads:[~2011-03-21 18:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 6:22 bug#8308: 23.3; Use utf-8 for writing abbrev file Leo
2011-03-21 9:00 ` Eli Zaretskii
2011-03-21 10:01 ` Leo
2011-03-21 10:54 ` Eli Zaretskii
2011-03-21 11:26 ` Andreas Röhler
2011-03-21 14:50 ` Stefan Monnier
2011-03-21 15:37 ` Leo
2011-03-21 18:45 ` Eli Zaretskii
2011-03-22 1:00 ` Leo
2011-03-22 2:48 ` Stefan Monnier
2011-03-22 3:47 ` Leo
2011-03-22 5:24 ` Stefan Monnier
2011-03-22 10:41 ` Leo
2011-03-22 18:27 ` Stefan Monnier
2011-03-23 0:42 ` Leo
2011-03-21 18:24 ` Andreas Röhler [this message]
2011-03-21 18:53 ` Eli Zaretskii
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=4D8797D0.3010109@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=bug-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.
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.