From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: request to revert the chnage of revno 112925 Date: Wed, 19 Jun 2013 08:59:24 -0400 Message-ID: References: <87k3lql3iy.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1371646774 29462 80.91.229.3 (19 Jun 2013 12:59:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Jun 2013 12:59:34 +0000 (UTC) Cc: emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 19 14:59:34 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UpHz2-0007dm-9U for ged-emacs-devel@m.gmane.org; Wed, 19 Jun 2013 14:59:32 +0200 Original-Received: from localhost ([::1]:49447 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpHz2-0001I0-0x for ged-emacs-devel@m.gmane.org; Wed, 19 Jun 2013 08:59:32 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53856) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpHyx-0001Hu-M3 for emacs-devel@gnu.org; Wed, 19 Jun 2013 08:59:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpHyw-0002RG-0z for emacs-devel@gnu.org; Wed, 19 Jun 2013 08:59:27 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:48637) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpHyv-0002RC-TW; Wed, 19 Jun 2013 08:59:25 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFFpZVy/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GwS2RCgOkeoFegxM X-IPAS-Result: Av4EABK/CFFFpZVy/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GwS2RCgOkeoFegxM X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="16708742" Original-Received: from 69-165-149-114.dsl.teksavvy.com (HELO pastel.home) ([69.165.149.114]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 19 Jun 2013 08:59:19 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 8F12262F1E; Wed, 19 Jun 2013 08:59:24 -0400 (EDT) In-Reply-To: <87k3lql3iy.fsf@gnu.org> (Kenichi Handa's message of "Wed, 19 Jun 2013 20:54:13 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:160660 Archived-At: > So, the above change does not improve the performance that much. The change was not done for performance reasons. > In addition, as iso-2022-jp and iso-2022-7bit have been the > most correctly detected coding systems in any environments, > there are many packages that uses them for *.el files (at > least in Japan). Now many of them doesn't work. Then maybe we should use a new coding-system which does falls back on iso-2022 if some incorrect utf-8 byte sequence is found? > In some sence, the above change is a regression because it > disables Emacs' facility to automatically decode ISO 2022 > based 7-bit encodings, and we should notify users about such > a change in advance, for instance, by showing warnings by > byte-compiler for non-UTF-8 and no-coding-tag *.el files for > a while (perhaps while Emacs' version is 24.*). I knew that the change was "risky". Admittedly, part of the motivation was to see how much breakage we'd bump into. But the core of what I want: make it so that utf-8 Elisp files are always recognized correctly, even in the absence of a coding: tag, and regardless of the user's locale. The way I implemented it broke recognition of iso-2022, but if there;s some other way that doesn't break it, that's even better. Stefan