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: Tue, 30 Aug 2022 10:29:08 +0300 Organization: LINKOV.NET Message-ID: <86o7w2196j.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35226"; 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: Eli Zaretskii , emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 30 09:32:01 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 1oSvj6-000915-PW for ged-emacs-devel@m.gmane-mx.org; Tue, 30 Aug 2022 09:32:00 +0200 Original-Received: from localhost ([::1]:36172 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oSvj5-0004Nn-RF for ged-emacs-devel@m.gmane-mx.org; Tue, 30 Aug 2022 03:31:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51196) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oSvh8-0002kN-HD for emacs-devel@gnu.org; Tue, 30 Aug 2022 03:29:58 -0400 Original-Received: from relay5-d.mail.gandi.net ([2001:4b98:dc4:8::225]:60243) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oSvh6-0002X2-Re; Tue, 30 Aug 2022 03:29:58 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id EA8171C000E; Tue, 30 Aug 2022 07:29:52 +0000 (UTC) In-Reply-To: <87ilnk8fuc.fsf@gmail.com> (Robert Pluim's message of "Tue, 26 Jul 2022 09:59:07 +0200") Received-SPF: pass client-ip=2001:4b98:dc4:8::225; envelope-from=juri@linkov.net; helo=relay5-d.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, 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:294324 Archived-At: > >>>> > Should we make `char-fold-to-regexp' into a command and refer to it > >>>> > from here? Or add something like `char-fold-show-equivalences'? > >>>> > >>>> A better name would be `describe-char-fold'. > >>> > >>> For a command, I'd say describe-character-foldings. But > >>> char-fold-show-equivalences is IMO a better name. > >> > >> All similar commands have names starting with the `describe-' prefix like > >> `describe-char', `describe-character-set'. So maybe then > >> `describe-char-fold-equivalences'. > > Juri> Ok, then let's use describe-char-fold-equivalences: > > Ah, that lists *all* the equivalences. I was thinking more along the > lines of the following (we can give it a different name, or combine them) The new command 'describe-char-fold-equivalences' that combines both approaches is pushed now. Thanks for helping to add this useful feature.