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: Tue, 26 Jul 2022 20:15:02 +0300 Message-ID: <835yjjdcdl.fsf@gnu.org> References: <165875050243.3275.8867100069985547389@vcs2.savannah.gnu.org> <20220725120142.D1283C0F203@vcs2.savannah.gnu.org> <87r1298hxp.fsf@gmail.com> <83v8rle28w.fsf@gnu.org> <8735eo829i.fsf@gmail.com> <83fsioc8uk.fsf@gnu.org> <87lesg6jgs.fsf@gmail.com> <838rofdfjy.fsf@gnu.org> <87zggv6chd.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="8521"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jul 26 19:17:37 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 1oGOBc-0001xE-9U for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Jul 2022 19:17:36 +0200 Original-Received: from localhost ([::1]:49242 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oGOBb-00033a-21 for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Jul 2022 13:17:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49358) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGO94-0000us-FJ for emacs-devel@gnu.org; Tue, 26 Jul 2022 13:14:58 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:42670) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGO94-0007BP-6S; Tue, 26 Jul 2022 13:14:58 -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=COEcvINO55fTnc6cJellvuT24iLtmWwX2O178iN/MBU=; b=efhdikU+TRd3zW0+k6c4 G/IqAhg9ztVxtbZHGVhSt0i6XW8r/mW+kGBo980Ap/RIf4NcQkiqA6JdpGcclhSaUlTLnGYx2OZfg tW48dii3uM+XLqPdHm+mJytQbUUm5Hts5cUAfjlqJUc+5hIi2rzxEMG8EtcQ22BLXdVlJ7DvnJgrA A1XBO3YKg8zTgclro8Mv4ho7x2+lLpTqXLalFoP3aENTL4RG8nqKp3H4DH2QJHeWvFChDhCJP8HkV S6r3X/f8uPlFk/4IAj/3bex+tZyWPM2k4nsMKUoD27WOXcGm7iM1SJL99kSwv1acDGAkOp0q/qu27 88eEKJAPtTDU4w==; Original-Received: from [87.69.77.57] (port=3268 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 1oGO93-00027o-D3; Tue, 26 Jul 2022 13:14:57 -0400 In-Reply-To: <87zggv6chd.fsf@gmail.com> (message from Robert Pluim on Tue, 26 Jul 2022 18:54:38 +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:292709 Archived-At: > From: Robert Pluim > Cc: emacs-devel@gnu.org > Date: Tue, 26 Jul 2022 18:54:38 +0200 > > Eli> Well, one question that it would be nice to be able to ask Emacs is > Eli> "show me all the characters that resemble CH", so that users could > Eli> decide what to add to the existing set. > > But the characters that resemble CH are already in the char-fold-table > by default. No, only those which we considered "safe" enough and which our heuristic collected. For example, ⒜ is by default not considered resembling 'a'. > And "chars that look like CH but arenʼt in the > char-fold-table" is something that a human can determine, but Iʼm all > out of ideas on how to do it in elisp. Look for characters whose decomposition has CH anywhere in the list? > Eli> Another potential issue is how does one easily delete a character from > Eli> the list, when what is known is its name or codepoint? Using Isearch > Eli> with \N{...} or "C-x 8 RET" is quite advanced. > > That sounds like we need a custom custom widget. I took a quick look, > but I didnʼt see an obvious way to have a widget which could display > its value(s) in several different formats. Like I said, I'm okay with status quo. Thanks.