From: Benjamin Riefenstahl <Benjamin.Riefenstahl@epost.de>
Subject: Re: GNU Emacs 21.3.50 : Problem in (point-min)
Date: Thu, 26 Jun 2003 15:39:18 +0200 [thread overview]
Message-ID: <m3ptl1ez5l.fsf@seneca.benny.turtle-trading.net> (raw)
In-Reply-To: <200306252001.h5PK1F0Z024543@hampton.math.ohio-state.edu> (Markus Rost's message of "Wed, 25 Jun 2003 16:01:15 -0400 (EDT)")
Hi Markus,
Markus Rost <rost@math.ohio-state.edu> 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
change.
> 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
next prev parent reply other threads:[~2003-06-26 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 20:01 GNU Emacs 21.3.50 : Problem in (point-min) Markus Rost
2003-06-26 9:25 ` Kai Großjohann
2003-06-26 14:02 ` Stephen J. Turnbull
2003-06-26 13:39 ` Benjamin Riefenstahl [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-23 10:35 Dhruva Krishnamurthy
2003-06-23 16:38 ` Benjamin Riefenstahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ptl1ez5l.fsf@seneca.benny.turtle-trading.net \
--to=benjamin.riefenstahl@epost.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).