From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Why is `C-x 8' limited to Latin-1 for search? Date: Mon, 10 Dec 2012 06:44:42 -0800 Message-ID: <9B10F36F6C4546408A98CE77D6EC55B2@us.oracle.com> References: <1992681966EA4AE4A56751FA335DD5CE@us.oracle.com> <871uey5zv6.fsf@mail.jurta.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1355150716 29284 80.91.229.3 (10 Dec 2012 14:45:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 10 Dec 2012 14:45:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: "'Juri Linkov'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 10 15:45:28 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ti4bm-0002TK-DS for ged-emacs-devel@m.gmane.org; Mon, 10 Dec 2012 15:45:26 +0100 Original-Received: from localhost ([::1]:56588 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ti4bZ-0006eM-PG for ged-emacs-devel@m.gmane.org; Mon, 10 Dec 2012 09:45:13 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:42790) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ti4bQ-0006ab-1j for emacs-devel@gnu.org; Mon, 10 Dec 2012 09:45:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ti4bK-0006GQ-2W for emacs-devel@gnu.org; Mon, 10 Dec 2012 09:45:03 -0500 Original-Received: from userp1040.oracle.com ([156.151.31.81]:28987) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ti4bJ-0006GD-Re for emacs-devel@gnu.org; Mon, 10 Dec 2012 09:44:57 -0500 Original-Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id qBAEitWr017718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 10 Dec 2012 14:44:57 GMT Original-Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id qBAEitTt021643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Dec 2012 14:44:55 GMT Original-Received: from abhmt117.oracle.com (abhmt117.oracle.com [141.146.116.69]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id qBAEitl4017464; Mon, 10 Dec 2012 08:44:55 -0600 Original-Received: from dradamslap1 (/71.202.147.44) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 10 Dec 2012 06:44:55 -0800 X-Mailer: Microsoft Office Outlook 11 In-reply-to: <871uey5zv6.fsf@mail.jurta.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Thread-Index: Ac3WrbxFW2fTwFtwQo6IgYh9hmq2cgANLuNw X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:155431 Archived-At: > 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': > > + (let* ((enable-recursive-minibuffers t) FWIW, I typically add such a binding not to a function like this but to functions that call it. `read-char-by-name' does not know whether it is being called from a minibuffer, i.e., whether it needs such a binding, but a function that calls it generally does know that. I don't think there is necessarily something wrong with doing what you suggest, so I have no objection. I just generally prefer to do only what the current code knows it needs. One could make an even more radical suggestion than yours: that `enable-recursive-minibuffers' simply be non-nil by default. (I am not suggesting that.) But the design intention in the past has been to not bind it to non-nil any more than necessary because it has been thought that recursive minibuffers entered accidentally can confuse users. I use mb-depth.el (which I tweak to use a simpler depth indicator and to let users customize it). That helps a lot wrt recursive minibuffers. The main confusion about recursive minibuffers is not knowing that you are in one or how deep it is. With mb-depth.el (which should be turned on by default, IMHO), I'm not sure how much the original design decision of avoiding non-nil `enable-recursive-minibuffers' is still appropriate/necessary.