all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Van Ly <van.ly@sdf.org>
Cc: 53896@debbugs.gnu.org
Subject: bug#53896: 28.0.91; Icomplete Vertical Mode fails to preview "C-x 8 RET 8072"
Date: Wed, 09 Feb 2022 16:36:33 +0200	[thread overview]
Message-ID: <83o83gumxa.fsf@gnu.org> (raw)
In-Reply-To: <f2fd6db1-e513-4b71-a3b6-a4f87e988e47@SDF.ORG> (message from Van Ly on Wed, 9 Feb 2022 10:38:29 +0000 (UTC))

tags 53896 notabug
thanks

> Date: Wed, 9 Feb 2022 10:38:29 +0000 (UTC)
> From: Van Ly <van.ly@sdf.org>
> 
> The vertical listing in the minibuffer in response to "insert-char" fails to preview the match for "C-x 8 RET 8072".
> 
> observed behavior
> * start by "emacs -Q"
> * M-x customize RET
> * search "icomplete vertical"
> * toggle "on" Icomplete Vertical Mode 
> * switch to "*scratch*" buffer
> ; --------------------------------
> ; minibuffer fails to preview 8072
> ; --------------------------------
> * C-x 8 RET
> * continue typing "80" ;; shows LINEAR A SIGN A580, A800, A801, A802, A803, A804, A805
> * continue typing "807" ;; shows LINEAR A SIGN A807
> * continue typing "8072" ;; shows "8072 [No matches]"

This has nothing to do with icomplete-vertical-mode.  You will see the
same with the default completion:

  C-x 8 RET 8072 TAB

This shows [No match].

The reason is that we deliberately remove all the CJG IDEOGRAPH-NNNN
names from the list of character names we submit to "C-x 8 RET" as
possible completions.  We do that because there are gobs of those
characters, whose names mean nothing (they are not real names), and
whose existence in the completions would just add a lot of noise.

This is a feature, not a bug.





  reply	other threads:[~2022-02-09 14:36 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 [this message]
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
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=83o83gumxa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53896@debbugs.gnu.org \
    --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.