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: Wed, 27 Jul 2022 22:55:15 +0300 Organization: LINKOV.NET Message-ID: <86o7xa4ado.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> <83v8rkcbm1.fsf@gnu.org> <867d3z9ewc.fsf@mail.linkov.net> <87mtcv55y7.fsf@gmail.com> <86ilni5rab.fsf@mail.linkov.net> <83y1we9x7b.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15862"; 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: rpluim@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 27 22:40:58 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 1oGnpy-0003x5-JU for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jul 2022 22:40:58 +0200 Original-Received: from localhost ([::1]:51276 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oGnpv-000512-MB for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jul 2022 16:40:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGnoU-00042K-Ae for emacs-devel@gnu.org; Wed, 27 Jul 2022 16:39:27 -0400 Original-Received: from relay1-d.mail.gandi.net ([217.70.183.193]:42907) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGnoP-000235-57; Wed, 27 Jul 2022 16:39:26 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id DC981240002; Wed, 27 Jul 2022 20:39:14 +0000 (UTC) In-Reply-To: <83y1we9x7b.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 27 Jul 2022 22:23:20 +0300") Received-SPF: pass client-ip=217.70.183.193; envelope-from=juri@linkov.net; helo=relay1-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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=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:292753 Archived-At: >> >> Why the user should not be allowed to see all active equivalences? >> > >> > We can always add an 'all' argument, but most people would be >> > searching for the equivalences for a particular character, I thought >> > (I have no evidence for this, but it seems like the obvious use-case). >> >> Wouldn't it be more natural instead of a special argument 'all' >> to add a 'char' argument that will describe the equivalences >> for a particular character, and when 'nil' then will describe >> all characters. > > Only if we believe that most users will want 'all'. Do we believe that most users want only describe-key, but not describe-bindings that describes all keys?