From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@gnu.org>,
"'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 13177@debbugs.gnu.org
Subject: bug#13177: 24.3.50; doc of `read-char-by-name'
Date: Fri, 21 Dec 2012 00:04:50 -0800 [thread overview]
Message-ID: <FC63EC335F61470388A782733D1A4C71@us.oracle.com> (raw)
In-Reply-To: <87d2y32641.fsf@gnu.org>
> > It's called "read-char-by-name", so the intention is pretty
> > clear: it should return a char.
>
> Agreed. I changed read-char-by-name on the trunk to signal
> an error for invalid input. (This also avoids other wonky cases,
> e.g. entering ## giving the empty symbol because `read-char-by-name'
> uses `read'...)
I don't understand why you did that, if you agree with Stefan. He proposed
making `completing-read' require input that represents a valid char. Why let
`completing-read' accept invalid input and then raise an error saying the input
is invalid?
Sorry, I don't get it - seems not very helpful.
The function should require the user to provide matching input (name or valid
code) or use `C-g' or `C-]' to cancel reading.
next prev parent reply other threads:[~2012-12-21 8:04 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
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 [this message]
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=FC63EC335F61470388A782733D1A4C71@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13177@debbugs.gnu.org \
--cc=cyd@gnu.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 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).