From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Juri Linkov'" <juri@jurta.org>
Cc: 13177@debbugs.gnu.org
Subject: bug#13177: 24.3.50; doc of `read-char-by-name'
Date: Sat, 15 Dec 2012 08:08:08 -0800 [thread overview]
Message-ID: <9D74DAC118B44C3DAF75A8CFC6AE7FB3@us.oracle.com> (raw)
In-Reply-To: <jwvfw37nz7r.fsf-monnier+emacs@gnu.org>
> >> Dunno just what the intention was for this function. If it really
> >> was to return a recognized Unicode character then this is a product
> >> bug and reading should not end until the user enters matching input
> >> (or hits `C-g').
>
> > As its docstring says, it also accepts a hexadecimal number
> > of Unicode code whose input can't use completion.
>
> That does not preclude using require-match.
Yes.
The problem for me is that I don't know what the intention (design) was or why.
Maybe someone has a good reason to return nil or to return a number that does
not correspond to a recognized code point?
The design should be clarified (and perhaps decided/changed, if appropriate)
before we try to fit the doc to it.
next prev parent reply other threads:[~2012-12-15 16:08 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9D74DAC118B44C3DAF75A8CFC6AE7FB3@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13177@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.