From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org, rms@gnu.org
Subject: Re: [reingold@emr.cs.iit.edu: Re: Character problems]
Date: Mon, 25 Mar 2002 21:58:52 +0200 [thread overview]
Message-ID: <7458-Mon25Mar2002215852+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <200203251202.g2PC26O03160@aztec.santafe.edu> (message from Richard Stallman on Mon, 25 Mar 2002 05:02:06 -0700 (MST))
> From: Richard Stallman <rms@gnu.org>
> Date: Mon, 25 Mar 2002 05:02:06 -0700 (MST)
>
> Can someone please work on this?
I don't see any problem; see below.
> Why would the workings of assoc (which has nothing to do with the
> display be affected?!!!
You may wish to look at the definition of standard-display-european
(on disp-table.el). (``Use the source, Luke!'' is still the best
policy, even with Emacs 21 ;-) There you will see that it does all
kinds of non-trivial things: makes your Emacs session a unibyte
session, possibly switches to a different language environment,
changes your terminal encoding, etc. These changes can easily modify
what the non-ASCII characters you type produce internally in Emacs.
So, the first time you type some character it is interpreted as a
multibyte Latin-1 character, but after you turn
standard-display-european on or off, the same character is interpreted
differently, e.g. as a single-byte unibyte code. Or vice versa. Thus
the failure in assoc: the list has some multibyte code, while you are
looking for a unibyte code in [0..255], or the other way around.
To see what is actually in the buffer, go to the offending character
and type "C-u C-x =". Emacs will show you what it knows about that
character. Do it for both a character in the list and the one you use
in assoc, and I'm sure you will see they are two different characters.
The moral? don't use standard-display-european. It's confusing and
unnecessary. There are better ways to do what it does.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
prev parent reply other threads:[~2002-03-25 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 12:02 [reingold@emr.cs.iit.edu: Re: Character problems] Richard Stallman
2002-03-25 19:58 ` Eli Zaretskii [this message]
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=7458-Mon25Mar2002215852+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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).