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 22:09:12 -0400 Message-ID: References: <51C1D83E.7020501@cs.ucla.edu> <51C21F78.2040307@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1371694163 787 80.91.229.3 (20 Jun 2013 02:09:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Jun 2013 02:09:23 +0000 (UTC) Cc: Kenichi Handa , emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 20 04:09:22 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 1UpUJN-0007j1-Pv for ged-emacs-devel@m.gmane.org; Thu, 20 Jun 2013 04:09:21 +0200 Original-Received: from localhost ([::1]:50914 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpUJN-0007IS-6K for ged-emacs-devel@m.gmane.org; Wed, 19 Jun 2013 22:09:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41661) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpUJJ-0007IM-J6 for emacs-devel@gnu.org; Wed, 19 Jun 2013 22:09:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpUJF-000572-IJ for emacs-devel@gnu.org; Wed, 19 Jun 2013 22:09:17 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:17007) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpUJF-00056w-Ek; Wed, 19 Jun 2013 22:09:13 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFFpZVy/2dsb2JhbABEDr8AF3OCHgEBBAFWIwULCzQSFBgNJIgeBsEtkQoDpHqBXoI5Wg X-IPAS-Result: Av4EABK/CFFFpZVy/2dsb2JhbABEDr8AF3OCHgEBBAFWIwULCzQSFBgNJIgeBsEtkQoDpHqBXoI5Wg X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="16766046" 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 22:09:07 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id 5E53E62D47; Wed, 19 Jun 2013 22:09:12 -0400 (EDT) In-Reply-To: <51C21F78.2040307@cs.ucla.edu> (Paul Eggert's message of "Wed, 19 Jun 2013 14:15:36 -0700") 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:160717 Archived-At: >> This is not specific to Elisp, of course, it's true of most programming >> languages > Yes, that sounds right. Should we make this change for all > programming-language files then? .c, .h, Makefile, etc.... Only for those languages that say so in the definition/standard/spec. > True, but in practice this means one should avoid putting NUL bytes in > such files. grep uses a heuristic that if a file contains a NUL byte, > it's considered to be a binary file, and by default grep won't output > the matching lines for that file. POSIX allows this behavior, and it's > common among many GNU and/or POSIX tools, which means it's typically > not a good idea to put NUL bytes in source files. Agreed, which is why it's very rare for Elisp files to have NUL bytes. But that's no reason to treat an Elisp file with a NUL bytes as being encoded in binary instead of utf-8 (which is the question under discussion here). Stefan