From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: luangruo@yahoo.com, 53896@debbugs.gnu.org
Subject: bug#53896: 28.0.91; Icomplete Vertical Mode fails to preview "C-x 8 RET 8072"
Date: Sun, 13 Feb 2022 18:38:02 +0200 [thread overview]
Message-ID: <83y22epvrp.fsf@gnu.org> (raw)
In-Reply-To: <80e659dc-1332-d89a-c8d4-1a9979a9f64@SDF.ORG> (message from Van Ly on Sun, 13 Feb 2022 14:34:41 +0000 (UTC))
> Date: Sun, 13 Feb 2022 14:34:41 +0000 (UTC)
> From: Van Ly <van.ly@sdf.org>
> cc: luangruo@yahoo.com, 53896@debbugs.gnu.org
>
> > The characters _are_ supported, and we do assign names to them (which
> > are trivially derived from their codepoints), so typing their names is
> > just an unnecessarily complicated way of typing their codepoint. IOW,
> > why not just type 8072 at "C-x 8 RET"s prompt, instead of selecting
> > "CJK IDEOGRAPH-8072" from a list of 27,000 candidates?
> >
>
> I do use 8072 at the "C-x 8 RET" prompt. The problem is it says:
>
> '''
> Insert character (Unicode name or hex): 8072 [No matches]
> '''
>
> And, I have to blindly hit RET at that point to insert the U+8072
> sign.
>
> What I expect to see is:
>
> '''
> Insert character (Unicode name or hex): 8072
> 聲 CJK UNIFIED IDEOGRAPH 8072
> '''
>
> And, I can then either hit RET at the end of 8072 or use the down
> arrow key to choose that line underneath.
How did you know to type "8072" to begin with?
next prev parent reply other threads:[~2022-02-13 16:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 10:38 bug#53896: 28.0.91; Icomplete Vertical Mode fails to preview "C-x 8 RET 8072" Van Ly
2022-02-09 14:36 ` Eli Zaretskii
2022-02-10 1:58 ` Van Ly
2022-02-10 4:54 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-11 23:11 ` Van Ly
2022-02-12 0:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 7:13 ` Eli Zaretskii
2022-02-12 7:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-13 13:06 ` Van Ly
2022-02-13 13:14 ` Eli Zaretskii
2022-02-13 13:18 ` Van Ly
2022-02-13 13:52 ` Eli Zaretskii
2022-02-13 14:18 ` Van Ly
2022-02-13 16:36 ` Eli Zaretskii
2022-02-14 14:55 ` Van Ly
2022-02-15 1:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-15 11:28 ` Van Ly
2022-02-13 14:34 ` Van Ly
2022-02-13 14:54 ` Andreas Schwab
2022-02-14 14:47 ` Van Ly
2022-02-14 14:57 ` Andreas Schwab
2022-02-14 15:01 ` Van Ly
2022-02-14 15:17 ` Andreas Schwab
2022-02-15 11:13 ` Van Ly
2022-02-15 11:33 ` Andreas Schwab
2022-02-15 21:25 ` Van Ly
2022-02-13 16:38 ` Eli Zaretskii [this message]
2022-02-14 14:57 ` Van Ly
2022-02-14 17:02 ` Eli Zaretskii
2022-02-15 11:21 ` Van Ly
2022-02-15 11:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-15 21:30 ` Van Ly
2022-02-22 1:38 ` Lars Ingebrigtsen
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=83y22epvrp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53896@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=van.ly@sdf.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 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.