From: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>
Subject: Re: Printing elisp char literals
Date: Tue, 27 May 2003 19:39:49 +0900 [thread overview]
Message-ID: <87ptm4isga.fsf@tleepslib.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <x57k8dtovh.fsf@lola.goethe.zz> (David Kastrup's message of "26 May 2003 22:49:22 +0200")
>>>>> "David" == David Kastrup <David.Kastrup@t-online.de> writes:
David> "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
David> writes:
>> Let's say I have an integer. How can I check whether it's a
>> char ?
Doesn't the optional argument to char-valid-p do the right thing?
And pretty clearly `event-modifiers' extracts the modifiers into a
Lispy format.
David> IIRC, XEmacs has sort of an opaque character representation
David> type, so it might be worth borrowing an idea or two from
David> them in this regard before reinventing the wheel. Stephen,
David> any idea of whether something might apply here?
Besides the fact that it looks like these APIs already exist, even for
more complex cases I don't think so. While I believe the XEmacs model
is a good one, it took several years to shake out many bugs due to
errors in porting code from the old "characters are a subset of
integers" model.
This would best be done in combination with a large revision of basic
Mule functionality, such as in emacs-unicode, if it's considered
desirable.
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
next prev parent reply other threads:[~2003-05-27 10:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 20:27 Printing elisp char literals Stefan Monnier
2003-05-26 20:49 ` David Kastrup
2003-05-27 10:39 ` Stephen J. Turnbull [this message]
2003-05-27 0:02 ` Miles' patch still fixes xfaces.c Robert J. Chassell
2003-05-27 22:40 ` Richard Stallman
2003-05-28 0:46 ` Robert J. Chassell
2003-05-31 19:52 ` Richard Stallman
2003-05-31 21:43 ` Robert J. Chassell
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=87ptm4isga.fsf@tleepslib.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).