From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Benjamin Riefenstahl Newsgroups: gmane.emacs.devel Subject: Re: GNU Emacs 21.3.50 : Problem in (point-min) Date: Thu, 26 Jun 2003 15:39:18 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200306252001.h5PK1F0Z024543@hampton.math.ohio-state.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=shift_jis Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1056635863 25313 80.91.224.249 (26 Jun 2003 13:57:43 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 26 Jun 2003 13:57:43 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Jun 26 15:57:41 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19VXEW-0006TA-00 for ; Thu, 26 Jun 2003 15:56:16 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19VXJ3-000328-00 for ; Thu, 26 Jun 2003 16:00:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19VXDh-0004IB-Uz for emacs-devel@quimby.gnus.org; Thu, 26 Jun 2003 09:55:25 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19VXC0-0003nG-MZ for emacs-devel@gnu.org; Thu, 26 Jun 2003 09:53:40 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19VX5Q-00022k-Td for emacs-devel@gnu.org; Thu, 26 Jun 2003 09:46:53 -0400 Original-Received: from [193.28.100.164] (helo=mail.epost.de) by monty-python.gnu.org with esmtp (Exim 4.20) id 19VWyJ-0007tG-Fr for emacs-devel@gnu.org; Thu, 26 Jun 2003 09:39:31 -0400 Original-Received: from seneca.benny.turtle-trading.net.epost.de (193.99.153.30) by mail.epost.de (6.7.015) id 3EC6EB40003AD6CD for emacs-devel@gnu.org; Thu, 26 Jun 2003 15:39:29 +0200 Original-To: emacs-devel@gnu.org In-Reply-To: <200306252001.h5PK1F0Z024543@hampton.math.ohio-state.edu> (Markus Rost's message of "Wed, 25 Jun 2003 16:01:15 -0400 (EDT)") User-Agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:15274 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:15274 Hi Markus, Markus Rost writes: > It happens for me also for other numbers.=20 Yes I see that now. I didn't investigate the issue besides just trying a few obvious numbers. I should have tried more *characters* instead, that's much more interesting ;-). > Buffer position 97 has nothing to do with character "a", so why > showing "?a" in the minibuffer?=20 Yes, you know that and I know that. But how is Emacs supposed to know, when both are represented exactly the same? Emacs could just display the number only (as it did before, I think), but than you'd have to figure out yourself what character is represented by e.g. 2276, in case you use a function that returns a character. You could argue that ELisp should use different types for characters and integers. But it doesn't, and I doubt that that is going to change. > By the way, when saving this mail, I was offered the following > coding system, apparently because of ?=9C=9B. > > Coding system for saving this buffer: > S -- shift_jis-unix (alias of japanese-shift-jis-unix) Sounds like a feature to me. Otherwise you could have lost the Japanese characters and/or I wouldn't have seen them here and I'd have had to guess what you are seeing. so long, benny