From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: Why is `C-x 8' limited to Latin-1 for search?
Date: Mon, 10 Dec 2012 09:45:09 +0200 [thread overview]
Message-ID: <871uey5zv6.fsf@mail.jurta.org> (raw)
In-Reply-To: <1992681966EA4AE4A56751FA335DD5CE@us.oracle.com> (Drew Adams's message of "Sat, 8 Dec 2012 20:52:52 -0800")
> To try the latter quickly (no, this is not the way to code this; it's just a
> quick way to let you try it):
>
> (unless (fboundp 'ORIG-isearch-edit-string)
> (defalias 'ORIG-isearch-edit-string
> (symbol-function 'isearch-edit-string)))
>
> (defun isearch-edit-string ()
> (interactive)
> (let ((enable-recursive-minibuffers t))
> (ORIG-isearch-edit-string)))
>
> In a buffer with some Unicode chars, e.g., `λ':
>
> C-s M-e C-x 8 RET GREEK SMALL LETTER LAMBDA C-s
>
> (You have completion for the character name, at least.)
Shouldn't users be able to insert Unicode characters in any minibuffer,
not only in `isearch-edit-string'? If these is no reason to disallow,
this patch should allow this for `completing-read' in `read-char-by-name':
=== modified file 'lisp/international/mule-cmds.el'
--- lisp/international/mule-cmds.el 2012-10-16 23:09:00 +0000
+++ lisp/international/mule-cmds.el 2012-12-10 07:43:46 +0000
@@ -2945,7 +2945,8 @@ (defun read-char-by-name (prompt)
This function also accepts a hexadecimal number of Unicode code
point or a number in hash notation, e.g. #o21430 for octal,
#x2318 for hex, or #10r8984 for decimal."
- (let ((input
+ (let* ((enable-recursive-minibuffers t)
+ (input
(completing-read
prompt
(lambda (string pred action)
next prev parent reply other threads:[~2012-12-10 7:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 4:52 Why is `C-x 8' limited to Latin-1 for search? Drew Adams
2012-12-09 5:33 ` Drew Adams
2012-12-10 7:46 ` Juri Linkov
2012-12-10 14:24 ` Drew Adams
2012-12-10 21:57 ` Juri Linkov
2012-12-11 0:11 ` Drew Adams
2012-12-10 7:45 ` Juri Linkov [this message]
2012-12-10 14:44 ` 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=871uey5zv6.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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 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.