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: No coding system in the modeline for unibyte buffers. Date: Fri, 16 Jan 2009 21:11:47 -0500 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1232158322 628 80.91.229.12 (17 Jan 2009 02:12:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 17 Jan 2009 02:12:02 +0000 (UTC) Cc: Emacs developers To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 17 03:13:15 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LO0gU-0006XJ-FX for ged-emacs-devel@m.gmane.org; Sat, 17 Jan 2009 03:13:14 +0100 Original-Received: from localhost ([127.0.0.1]:47812 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LO0fD-0004GU-AW for ged-emacs-devel@m.gmane.org; Fri, 16 Jan 2009 21:11:55 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LO0f9-0004GN-FE for emacs-devel@gnu.org; Fri, 16 Jan 2009 21:11:51 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LO0f7-0004GB-1j for emacs-devel@gnu.org; Fri, 16 Jan 2009 21:11:50 -0500 Original-Received: from [199.232.76.173] (port=43812 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LO0f6-0004G8-Sw for emacs-devel@gnu.org; Fri, 16 Jan 2009 21:11:48 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:57909 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LO0f6-0002d0-KC for emacs-devel@gnu.org; Fri, 16 Jan 2009 21:11:48 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgoFAAPNcElMCpxj/2dsb2JhbACBasouhXKBfw X-IronPort-AV: E=Sophos;i="4.37,278,1231131600"; d="scan'208";a="32438970" Original-Received: from 76-10-156-99.dsl.teksavvy.com (HELO pastel.home) ([76.10.156.99]) by ironport2-out.teksavvy.com with ESMTP; 16 Jan 2009 21:11:47 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 8264C7F97; Fri, 16 Jan 2009 21:11:47 -0500 (EST) In-Reply-To: (Juanma Barranquero's message of "Sat, 17 Jan 2009 00:47:11 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107920 Archived-At: > IIUC, a unibyte buffer should contain raw bytes, while a raw-text > multibyte buffer would contain the same contents, converted to the > internal utf-8 based Emacs representation. Actually the raw-text part of a multibyte buffer only affects operation when it is saved and loaded, so it can contain characters that are not bytes. > But I confess I'm puzzled why > M-x find-file-binary test.txt > M-: enable-multibyte-characters =3D> nil > C-u C-x =3D ; over =F1 > character: (241, #o361, #xf1) > preferred charset: iso-8859-1 (Latin-1 (ISO/IEC 8859-1)) > code point: 0xF1 > syntax: w which means: word > category: j:Japanese l:Latin > buffer code: #xC3 #xB1 > file code: #xC3 #xB1 (encoded by coding system no-conversion) > If I'm hopelessly wrong, I'm quite ready to be enlightened (and > perhaps the docs will need work). Indeed that's a bug in C-u C-x =3D. It should pay attention to the buffer's enable-multibyte-characters and then present #xf1 not as a latin-1 char but as a raw-byte. Stefan