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, 27 Jul 2022 14:32:57 +0300 Message-ID: <83ilnibxjq.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> <83v8rkcbm1.fsf@gnu.org> <867d3z9ewc.fsf@mail.linkov.net> <87mtcv55y7.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24983"; 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 Jul 27 13:34:05 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 1oGfIh-0006Fl-Qs for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jul 2022 13:34:03 +0200 Original-Received: from localhost ([::1]:60070 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oGfIg-0007tz-NL for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jul 2022 07:34:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40934) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGfHW-0006Sp-Sh for emacs-devel@gnu.org; Wed, 27 Jul 2022 07:32:51 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57558) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGfHW-0007vB-64; Wed, 27 Jul 2022 07:32:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=lVWFkiLLFHULrq2urldVerh5DmWedWFnq6Hl9L3GU9w=; b=M4m1gGj623Fv byuTOQxifmdlyYRL1DrKEB+QmDG3Ooyd4Xj3SC0yhEiovOLwQbjaH5y3WqPk2PKkgwJrqPTyXx5as gYEO1qu/Kh5VEYlc/8pxNIcujJmRe80pTRyC+2YNb3xTj3Lpzo5vsXygMR8BJOXRJm5U+IXZZsm4M xaknU9bK8nyhJcHRtmDMuuDgBng5DN21a8A5xnwAyy8rFxyc0ZVK1TfbSoRZtZJ5MonimHgjj4XoR jAnWjJNJX6hB9RkRrNyIUwvLNNwq5tKA8cbTD1qGFbreqKSd4Ql82vpNj8NPKRfpTgvoRlqTtYx07 2i6uiSxeChPTHJq9YAjVQQ==; Original-Received: from [87.69.77.57] (port=2987 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 1oGfHV-0007E2-K8; Wed, 27 Jul 2022 07:32:49 -0400 In-Reply-To: <87mtcv55y7.fsf@gmail.com> (message from Robert Pluim on Wed, 27 Jul 2022 10:13:20 +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:292741 Archived-At: > From: Robert Pluim > Cc: Eli Zaretskii , emacs-devel@gnu.org > Date: Wed, 27 Jul 2022 10:13:20 +0200 > > >>>>> On Wed, 27 Jul 2022 10:46:27 +0300, Juri Linkov said: > > >>>> 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) > >> > >> I indeed think we should only show the equivalence sequences of a > >> single character. Showing all of them is too much. > > Juri> 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). That was also my impression.