From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs-28 a866674b2a: Fix inaccuracies in "lax search" documentation Date: Wed, 31 Aug 2022 19:40:10 +0300 Message-ID: <83ilm8s6xh.fsf@gnu.org> 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> <87edwwjrp4.fsf@gmail.com> 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="6734"; mail-complaints-to="usenet@ciao.gmane.io" Cc: juri@linkov.net, emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 31 18:45:10 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 1oTQpx-0001b7-Ji for ged-emacs-devel@m.gmane-mx.org; Wed, 31 Aug 2022 18:45:09 +0200 Original-Received: from localhost ([::1]:55844 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oTQpw-0004xb-31 for ged-emacs-devel@m.gmane-mx.org; Wed, 31 Aug 2022 12:45:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47360) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTQkj-0005bB-Vo for emacs-devel@gnu.org; Wed, 31 Aug 2022 12:39:46 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47514) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTQkj-0004P0-JP; Wed, 31 Aug 2022 12:39:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=tz9zzJkyoBjK7lrB0t5NriSYIF/+28SfVf/UiPoTOGQ=; b=e6LZKs/RaMUzxucloYE8 G1pCt1xL+TeW3WaDjGfZB+j40hLegITZHS67ek3chixRi9s7q41cDldTr1V5tphHjH5FclSB+Huxz HJ4Vuh/yK8mqTpzcgQEl5X/A9CYITXGarJgXWVrjqQXQTTsZLSPr1m6zTkCrJ+UHh0ULuzyCPFrjY lFFWVEeRAU+yx7q2iFOK+KqssZhBo9wcx4VzuTWwLgTnxLFqWD8wJXtiTk7fq3RxPBxOQ5pVOQdyL 8K2X8l/vLqclkVl+OhbkSrP89SvYDEq3lh55e5WfTbb55Z0pGmg5CrZSZnoXGe7AxbZPLuaOoJ9LP 156hulCsrEp1BQ==; Original-Received: from [87.69.77.57] (port=2226 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTQkj-0006gG-2Q; Wed, 31 Aug 2022 12:39:45 -0400 In-Reply-To: <87edwwjrp4.fsf@gmail.com> (message from Robert Pluim on Wed, 31 Aug 2022 18:36:23 +0200) 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:294445 Archived-At: > From: Robert Pluim > Cc: Eli Zaretskii , emacs-devel@gnu.org > Date: Wed, 31 Aug 2022 18:36:23 +0200 > > >>>>> On Wed, 31 Aug 2022 19:09:34 +0300, Juri Linkov said: > > >> 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'. > > Juri> Wouldn't it be cleaner to use just (read-char-from-minibuffer "Character: ") > Juri> where you can either type a character directly or use 'C-x 8 RET' > Juri> to insert a character by its name. > > I guess that works as well, but then youʼre assuming knowledge of 'C-x > 8 RETʼ. I canʼt come up with a strong argument either ways, so Iʼm > going to chicken out here and see what Eli says ☺️ Eli says that he was mightily surprised to see that just typing a character at the prompt didn't take that character literally, but instead interpreted it as a hex codepoint.