From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: request to revert the chnage of revno 112925 Date: Wed, 19 Jun 2013 09:11:42 -0700 Organization: UCLA Computer Science Department Message-ID: <51C1D83E.7020501@cs.ucla.edu> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1371658318 3719 80.91.229.3 (19 Jun 2013 16:11:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Jun 2013 16:11:58 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org To: Kenichi Handa Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 19 18:11:57 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 1UpKz8-0004Ou-88 for ged-emacs-devel@m.gmane.org; Wed, 19 Jun 2013 18:11:50 +0200 Original-Received: from localhost ([::1]:44872 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpKz7-000879-Ot for ged-emacs-devel@m.gmane.org; Wed, 19 Jun 2013 12:11:49 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45082) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpKz4-00086z-60 for emacs-devel@gnu.org; Wed, 19 Jun 2013 12:11:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpKz2-00076W-MH for emacs-devel@gnu.org; Wed, 19 Jun 2013 12:11:46 -0400 Original-Received: from smtp.cs.ucla.edu ([131.179.128.62]:36582) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpKz2-00074P-Cp; Wed, 19 Jun 2013 12:11:44 -0400 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 918F939E8106; Wed, 19 Jun 2013 09:11:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu Original-Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2J4NiilhTkQk; Wed, 19 Jun 2013 09:11:42 -0700 (PDT) Original-Received: from [192.168.1.9] (pool-71-108-49-126.lsanca.fios.verizon.net [71.108.49.126]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id DC63F39E8100; Wed, 19 Jun 2013 09:11:42 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 In-Reply-To: X-Enigmail-Version: 1.5.1 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 131.179.128.62 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:160680 Archived-At: On 06/19/2013 08:35 AM, Kenichi Handa wrote: > I'd like to find a better solution, but at first please > clarify the requirements. I assume these requirements should be the same for Elisp files as for other files that Emacs is asked to read; if not, could this be clarified? > * What to do with an ASCII file? Previously find-file for > such a file results in undecided-xxx > buffer-file-coding-system. Now it's utf-8-xxx. To help think this through, could you please explain the practical consequences of this change? If I edit a file that's undecided-xxx, and insert a character that can be encoded either as UTF-8 or as ISO-2022-JP say, the buffer becomes utf-8-xxx, right? So in that scenario there is not much practical difference. What scenarios entail significant differences depending on whether the file is undecided-xxx or utf-8-xxx? > * What to do with an invalid UTF-8 file. Previously, > find-file detects a proper coding-system for such a file. > Now utf-8 is forced and any invalid UTF-8 byte sequences > are decoded as raw bytes. Surely this should be fixed: the file should be decoded properly, as before. > * What to do with null byte detection. Previously, if a > *.el file contains a null byte and > inhibit-null-byte-detection is nil (the default), it's > detected as a binary file. Now utf-8 is forced regardless > of inhibit-null-byte-detection. I suggest going back to the old behavior (that's the normal behavior for random files that Emacs edits, right?). Elisp files normally don't contain null bytes; such files are not considered to be text files in the POSIXish world.