From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Xue Fuqiao Newsgroups: gmane.emacs.devel Subject: Re: Loading souce Elisp faster Date: Mon, 25 Feb 2013 21:50:38 +0800 Organization: The Church of Emacs Message-ID: <20130225215038.ab62ebb7b21a755178fb2848@gmail.com> References: <877glwtt5i.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1361800286 9441 80.91.229.3 (25 Feb 2013 13:51:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 Feb 2013 13:51:26 +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 Mon Feb 25 14:51:49 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 1U9yT6-0007KQ-KO for ged-emacs-devel@m.gmane.org; Mon, 25 Feb 2013 14:51:48 +0100 Original-Received: from localhost ([::1]:50677 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9ySm-0005y9-07 for ged-emacs-devel@m.gmane.org; Mon, 25 Feb 2013 08:51:28 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:59254) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9ySN-00057l-Pa for emacs-devel@gnu.org; Mon, 25 Feb 2013 08:51:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U9ySI-0004gS-9m for emacs-devel@gnu.org; Mon, 25 Feb 2013 08:51:03 -0500 Original-Received: from mail-pb0-f54.google.com ([209.85.160.54]:33556) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U9yS9-0004bz-Ie; Mon, 25 Feb 2013 08:50:49 -0500 Original-Received: by mail-pb0-f54.google.com with SMTP id rr4so1682840pbb.27 for ; Mon, 25 Feb 2013 05:50:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:in-reply-to :references:organization:x-mailer:mime-version:content-type :content-transfer-encoding; bh=zN4pnj67WR1Jzos3+KKwjkOw6WFUB+u+LjQ/6lgfPsw=; b=EUb53RdJiY8KuLk/be99GnBZ4RzyiMVO+z9PJNTNbJ17YZWhmk75NOXcvJd7hBVplX bUP/nw9a3hDZ4E8uDoQjUZXpMGuMK+sEp37A054KABikXeI0O9rsagXy9/0dNHPZB/kY 5RJDfM6WPjjeGXkghuZda+4kdtXMdT7YX62Hvs2aAQYHijhSlNIOmJUYUmukg8pG8bhZ jZXsYIAlHQKbv0TSP39yXolkfg1B87ZeMHS/5ck4Xpb3nWdEST5+/lMnO35ZKp0g9MCp HYRAdcY7bw4e9Wq4eFQ3IVLRsO5SY/x08vAY1B1zG5DuOWCmXZ0HehDHJaidn0LWECfX shVg== X-Received: by 10.66.164.133 with SMTP id yq5mr18752766pab.160.1361800247034; Mon, 25 Feb 2013 05:50:47 -0800 (PST) Original-Received: from Emacs ([123.114.126.135]) by mx.google.com with ESMTPS id xr3sm12798001pbc.46.2013.02.25.05.50.42 (version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Feb 2013 05:50:45 -0800 (PST) In-Reply-To: <877glwtt5i.fsf@gnu.org> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.13; x86_64-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 209.85.160.54 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:157317 Archived-At: On Mon, 25 Feb 2013 22:33:29 +0900 Kenichi Handa wrote: > In article , Stefan Monnier writes: > > So basically, all we need to do is to be able to easily recognize "Elisp > > source in utf-8 encoding". One way to do that would be to use > > a BOM-like marker, e.g. start utf-8 Elisp files with "\ufeff" either at > > the very beginning of the file or right after a semi-colon (for better > > backward compatibility). > We can have "coding: utf-8;" tag at the first line. Isn't it > enough? Yes, we can. But most Elisp source files have already been in utf-8 encoding. In (info "(elisp) Coding Conventions"): If your program contains non-ASCII characters in string or character constants, you should make sure Emacs always decodes these characters the same way, regardless of the user's settings. The easiest way to do this is to use the coding system `utf-8-emacs' (*note Coding System Basics::), and specify that coding in the `-*-' line or the local variables list. Maybe this can be changed now (or in the near future), because of the "99% utf-8 future". -- Best regards, Xue Fuqiao. http://www.emacswiki.org/emacs/XueFuqiao