From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16216@debbugs.gnu.org
Subject: bug#16216: 24.3.50; <control> entries in `ucs-names'
Date: Sat, 21 Dec 2013 21:08:35 -0800 (PST) [thread overview]
Message-ID: <c5300bec-e436-4582-8c15-307d07343c47@default> (raw)
In-Reply-To: <<83lhzd8roz.fsf@gnu.org>>
> Look at UnicodeData.txt, near the beginning of the file.
I see; thanks. And I recall now that you pointed me to that
file once before.
Still, that does not really answer the questions I posed, AFAICT.
At least not for a user of `ucs-names' or the other functions
mentioned.
If `ucs-names' essentially corresponds to UnicodeData.txt, how
about citing that in its doc? Better yet, perhaps cite this,
which seems to be the place that the fields of UnicodeData.txt
are described:
http://www.unicode.org/Public/5.1.0/ucd/UCD.html#UnicodeData.txt
Still, part of my question is about `insert-char' and
`read-char-by-name', which is really what most users will see.
(Those are admittedly not the same as `ucs-names'. But they are
currently the only consumers of the latter.)
Should the `<control>' entries of `ucs-names' be included for
the completion provided by `read-char-by-name'? You can only
choose one of them, anyway. What is the use case for that -
the reason it is included as a possibility for `C-x 8 RET'?
next parent reply other threads:[~2013-12-22 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<cbbc5d36-76a4-4145-9dbe-30f8c986b2a7@default>
[not found] ` <<83lhzd8roz.fsf@gnu.org>
2013-12-22 5:08 ` Drew Adams [this message]
2013-12-22 5:10 ` bug#16216: 24.3.50; <control> entries in `ucs-names' Drew Adams
2013-12-22 18:13 ` Eli Zaretskii
2013-12-22 18:10 ` Eli Zaretskii
2013-12-22 2:09 Drew Adams
2013-12-22 3:55 ` Eli Zaretskii
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=c5300bec-e436-4582-8c15-307d07343c47@default \
--to=drew.adams@oracle.com \
--cc=16216@debbugs.gnu.org \
--cc=eliz@gnu.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).