[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU Emacs 21.3.50 : Problem in (point-min)

From: Benjamin Riefenstahl
Subject: Re: GNU Emacs 21.3.50 : Problem in (point-min)
Date: Thu, 26 Jun 2003 15:39:18 +0200
User-agent: Gnus/5.1001 (Gnus v5.10.1) Emacs/21.3.50 (gnu/linux)

Hi Markus,

Markus Rost <address@hidden> writes:
> It happens for me also for other numbers. 

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? 

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

> By the way, when saving this mail, I was offered the following
> coding system, apparently because of ?悍.
> 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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]