From: Juri Linkov <juri@jurta.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 13177@debbugs.gnu.org
Subject: bug#13177: 24.3.50; doc of `read-char-by-name'
Date: Sun, 16 Dec 2012 12:49:49 +0200 [thread overview]
Message-ID: <87wqwijmpe.fsf@mail.jurta.org> (raw)
In-Reply-To: <m2wqwil2qk.fsf@igel.home> (Andreas Schwab's message of "Sun, 16 Dec 2012 11:18:11 +0100")
>> (insert-char (read-char))
>>
>> and type `C-SPC'. It inserts the character ^@ with the value 0.
>
> That's the correct value for C-SPC.
Yes, I was confused by the docstring of `read-char' that says:
If the character has modifiers, they are resolved and reflected to the
character code if possible (e.g. C-SPC -> 0).
But nevertheless `read-char' can return non-characters numbers unacceptable
for `insert-char'. Currently `read-char-by-name' does the same. e.g.:
M-: (insert-char (read-char)) RET C-M-SPC
reports:
(wrong-type-argument characterp 134217728)
and
M-: (insert-char (read-char-by-name "Insert character (Unicode name or hex): "))
RET #x8000000 RET
reports the same:
(wrong-type-argument characterp 134217728)
So we are trying to fix a non-problem.
next prev parent reply other threads:[~2012-12-16 10:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 4:01 bug#13177: 24.3.50; doc of `read-char-by-name' Drew Adams
2012-12-15 11:09 ` Juri Linkov
2012-12-15 14:54 ` Stefan Monnier
2012-12-15 15:18 ` Juri Linkov
2012-12-15 15:47 ` Stefan Monnier
2012-12-15 16:08 ` Drew Adams
2012-12-15 23:20 ` Stefan Monnier
2012-12-15 23:39 ` Drew Adams
2012-12-16 9:12 ` Juri Linkov
2012-12-16 10:18 ` Andreas Schwab
2012-12-16 10:49 ` Juri Linkov [this message]
2012-12-16 16:34 ` Drew Adams
2012-12-16 16:31 ` Drew Adams
2012-12-21 7:53 ` Chong Yidong
2012-12-21 8:04 ` Drew Adams
2012-12-15 15:52 ` Drew Adams
2012-12-15 16:08 ` Eli Zaretskii
2012-12-15 16:23 ` Drew Adams
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=87wqwijmpe.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=13177@debbugs.gnu.org \
--cc=schwab@linux-m68k.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).