From: Richard Stallman <rms@gnu.org>
Cc: handa@m17n.org, emacs-devel@gnu.org
Subject: Re: char-table-range
Date: Fri, 20 Feb 2004 08:42:21 -0500 [thread overview]
Message-ID: <E1AuAv7-0001r9-Nv@fencepost.gnu.org> (raw)
In-Reply-To: <200402190128.i1J1StG21175@raven.dms.auburn.edu> (message from Luc Teirlinck on Wed, 18 Feb 2004 19:28:55 -0600 (CST))
I did not realize that currently, for charsets different from ascii and
eight-bit-{control,graphic}, char-table-range actually returns the
entire range of values if the value is not uniform.
That seems like a good thing for it to to.
Yes, but Handa remarked that the return value is given in a form
(sub-char-table) which is not supposed to be exported to Lisp.
That is unfortunate. The distinction between char-tables and
sub-char-tables is one that "sort of grew", and is sill being
clarified.
I am currently reading the Elisp chapter on sequences. In the section
on chartables several things are wrongly, incompletely or ambiguously
documented. I will take care of that, but I do not want to "document"
bugs.
Thank you.
Setting the default value using `set-char-table-default' does _not_
override non-nil pre-existing values in the charset _except_ for the
generic character itself. Setting the generic character itself
overrides the entire charset. Is this intentional?
I don't know. But it is not very clean, so it would be nice to change it,
if that does not cause some other problem.
Handa, do you know if anything depends on this?
The second thing that looks _somewhat_ strange (but maybe it is OK) is
that (make-char-table subtype init) will also set extra slots to INIT.
This is somewhat unexpected because a logical default for characters
would seldom seem to make sense for extra slots as well. Maybe this
is intentional anyway.
It looks like a misfeature to me. But before changing it, we had
better see if anything depends on it. I think that means looking at
all the calls to make-char-table and checking each one.
Can you do that?
next prev parent reply other threads:[~2004-02-20 13:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 0:43 char-table-range Kenichi Handa
2004-02-16 1:30 ` char-table-range Luc Teirlinck
2004-02-18 23:38 ` char-table-range Richard Stallman
2004-02-19 1:28 ` char-table-range Luc Teirlinck
2004-02-19 15:40 ` char-table-range Luc Teirlinck
2004-02-20 13:42 ` Richard Stallman [this message]
2004-02-21 0:03 ` char-table-range Luc Teirlinck
[not found] ` <200403020247.LAA16492@etlken.m17n.org>
2004-03-03 3:39 ` char-table-range Luc Teirlinck
2004-03-03 4:50 ` char-table-range Kenichi Handa
2004-03-04 16:41 ` char-table-range Richard Stallman
2004-03-03 4:51 ` char-table-range Kenichi Handa
2004-02-19 1:52 ` char-table-range Luc Teirlinck
2004-02-20 13:42 ` char-table-range Richard Stallman
2004-02-16 2:12 ` char-table-range Luc Teirlinck
2004-02-16 4:08 ` char-table-range Kenichi Handa
2004-02-18 17:55 ` char-table-range Richard Stallman
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=E1AuAv7-0001r9-Nv@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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).