From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: Editing exportet registry files
Date: Thu, 07 Jul 2005 15:25:00 +0900 [thread overview]
Message-ID: <E1DqPoi-0002zr-00@etlken> (raw)
In-Reply-To: <f7ccd24b050706172858123cbe@mail.gmail.com> (message from Juanma Barranquero on Thu, 7 Jul 2005 02:28:39 +0200)
In article <f7ccd24b050706172858123cbe@mail.gmail.com>, Juanma Barranquero <lekktu@gmail.com> writes:
> Am I the only one who gets this error?
>> emacs -Q
>>
>> M-x ielm <RET>
ELISP> (prefer-coding-system 'utf-16le-with-signature)
>> (mule-utf-16le-with-signature-dos . mule-utf-16le-with-signature-unix)
>>
ELISP> (list-coding-systems)
>> *** Eval error *** Cannot open load file: mule-diag
ELISP>
This is because prefer-coding-system sets also
default-file-name-coding-system. It seems that any attempt
to set it (and keyboard-coding-system) to ascii-incompatible
coding system should be avoided. So, I've just installed
these changes.
2005-07-07 Kenichi Handa <handa@m17n.org>
* international/mule.el (make-coding-system): Describe
`ascii-incompatible' property in the docstring.
(set-file-name-coding-system): Signal an error if coding-system is
ascii-incompatible.
(set-keyboard-coding-system): Likewise.
* international/mule-cmds.el (set-default-coding-systems): Don't
set default-file-name-coding-system and
default-keyboard-coding-system if coding-system is
ASCII-incompatible.
* international/utf-16.el: Declare that all UTF-16-based coding
systems ASCII-incompatible.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2005-07-07 6:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 9:02 Editing exportet registry files Dhruva Krishnamurthy (RBIN/EDI3) *
2005-07-01 9:49 ` gritsch
2005-07-01 11:02 ` Mathias Dahl
2005-07-01 13:13 ` Juanma Barranquero
2005-07-02 14:50 ` Juanma Barranquero
2005-07-02 14:55 ` Juanma Barranquero
2005-07-02 16:07 ` Juanma Barranquero
2005-07-07 0:28 ` Juanma Barranquero
2005-07-07 6:25 ` Kenichi Handa [this message]
2005-07-07 9:09 ` Juanma Barranquero
2005-07-07 9:55 ` Juanma Barranquero
2005-07-07 12:36 ` Kenichi Handa
2005-07-07 13:35 ` Juanma Barranquero
2005-07-07 18:56 ` Benjamin Riefenstahl
2005-07-07 19:34 ` Gaëtan LEURENT
2005-07-07 21:32 ` Benjamin Riefenstahl
2005-07-08 0:15 ` Juanma Barranquero
2005-07-08 1:42 ` Kenichi Handa
2005-07-11 9:37 ` Juanma Barranquero
2005-07-08 1:52 ` Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2005-06-30 20:27 Markus Gritsch
2005-06-30 21:23 ` Stefan Monnier
2005-07-01 7:12 ` gritsch
2005-07-01 8:17 ` Miles Bader
2005-07-01 8:24 ` Juanma Barranquero
2005-07-01 17:45 ` David Kastrup
2005-07-01 18:01 ` Juanma Barranquero
2005-07-01 18:52 ` Gaëtan LEURENT
2005-07-01 23:25 ` Juanma Barranquero
2005-07-01 22:12 ` Jason Rumney
2005-07-01 23:38 ` Juanma Barranquero
2005-07-02 11:50 ` Andreas Schwab
2005-07-02 14:33 ` Juanma Barranquero
2005-07-03 19:52 ` Gaëtan LEURENT
2005-07-03 21:34 ` Jason Rumney
2005-07-03 21:48 ` David Kastrup
2005-07-04 7:43 ` Kaloian Doganov
2005-07-01 8:28 ` gritsch
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=E1DqPoi-0002zr-00@etlken \
--to=handa@m17n.org \
--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).