From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: emacs-28 a866674b2a: Fix inaccuracies in "lax search" documentation Date: Thu, 01 Sep 2022 10:22:55 +0300 Organization: LINKOV.NET Message-ID: <861qsvef9w.fsf@mail.linkov.net> References: <165875050243.3275.8867100069985547389@vcs2.savannah.gnu.org> <20220725120142.D1283C0F203@vcs2.savannah.gnu.org> <87r1298hxp.fsf@gmail.com> <864jz513nb.fsf@mail.linkov.net> <83h735dpno.fsf@gnu.org> <86tu75doeq.fsf@mail.linkov.net> <867d41dlc8.fsf@mail.linkov.net> <87ilnk8fuc.fsf@gmail.com> <86o7w2196j.fsf@mail.linkov.net> <87mtbkkdb5.fsf@gmail.com> <867d2ol9yl.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20549"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: Robert Pluim , Eli Zaretskii , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 01 10:11:31 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oTfIP-0005CH-DN for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Sep 2022 10:11:29 +0200 Original-Received: from localhost ([::1]:38934 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oTfIO-0004If-Bb for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Sep 2022 04:11:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59908) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTehq-0002ce-Jy for emacs-devel@gnu.org; Thu, 01 Sep 2022 03:33:43 -0400 Original-Received: from relay11.mail.gandi.net ([217.70.178.231]:34239) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTeho-0000jX-Gg; Thu, 01 Sep 2022 03:33:42 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id 290CB100002; Thu, 1 Sep 2022 07:33:32 +0000 (UTC) In-Reply-To: (Stefan Monnier's message of "Wed, 31 Aug 2022 16:14:54 -0400") Received-SPF: pass client-ip=217.70.178.231; envelope-from=juri@linkov.net; helo=relay11.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:294470 Archived-At: >>> I have one comment: using `read-char-by-name' is kind >>> of cumbersome when all you want to do is find the equivalents to >>> e.g. 'a'. Would it make sense to have something similar to >>> `read-char-by-name' but that accepted single characters *without* >>> treating those as hex? Youʼd still be able to enter single digit >>> hex characters by prefixing them with '0'. >> Wouldn't it be cleaner to use just (read-char-from-minibuffer "Character: ") >> where you can either type a character directly or use 'C-x 8 RET' >> to insert a character by its name. > > I lost the beginning of this discussion: why can't we unify > `read-char-from-minibuffer` and `read-char-by-name' into a single function? Robert sent a patch that does this by adding a new arg ALLOW-SINGLE to `read-char-by-name'.