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:04 +0300 Message-ID: <83k07ybxl7.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> <835yjjdcdl.fsf@gnu.org> <87v8rj56ta.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="22110"; 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 Wed Jul 27 13:33:40 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 1oGfIJ-0005Zb-Sv for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jul 2022 13:33:40 +0200 Original-Received: from localhost ([::1]:59112 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oGfII-0007FZ-Bk for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jul 2022 07:33:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40822) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGfGi-00069b-3n for emacs-devel@gnu.org; Wed, 27 Jul 2022 07:32:01 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:57544) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGfGh-0007jG-1l; Wed, 27 Jul 2022 07:31:59 -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=9abBsqTJXVK/z+g6yjdF6jIvfP5Pl7sChk7rFqOf45w=; b=ibY226e4IQmRQR9QtojJ ULNcSTr+tbOkZsaJUQynvQPuwb9ssTEdH85CIcr1BQHxQ/TzRBS2ktMZAeEnUbYalSTImtCqp94Cw TdGuKsDXnky12XfOIZMG+8cKTsnBGz8ZC/Xb5mtpC/x7jcs7eyx3GSCKTMpjnY3uJbnUSTncv/fYx 4eCDQuiDa6WBjhHFYtl3uiVn2W6oIefjFHKuLxyE6TePfGJSXHkPoy6kWSdgqgUqHLvNM6djsG/Vl sK4ctdz3F8rce4Q79o9CDw2Dm6EzfqZ8K5OVjMp3TUwDwkOKH5tIHE3zpsXUmQKOm9awbBDum2EzB wYq/3eY2NmTzKQ==; Original-Received: from [87.69.77.57] (port=2933 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 1oGfGe-0005Px-Vb; Wed, 27 Jul 2022 07:31:58 -0400 In-Reply-To: <87v8rj56ta.fsf@gmail.com> (message from Robert Pluim on Wed, 27 Jul 2022 09:54:41 +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:292740 Archived-At: > From: Robert Pluim > Cc: emacs-devel@gnu.org > Date: Wed, 27 Jul 2022 09:54:41 +0200 > > >>>>> On Tue, 26 Jul 2022 20:15:02 +0300, Eli Zaretskii said: > > 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. > > Eli> No, only those which we considered "safe" enough and which our > Eli> heuristic collected. For example, ⒜ is by default not considered > Eli> resembling 'a'. > > OK > > >> 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. > > Eli> Look for characters whose decomposition has CH anywhere in the list? > > I thought we already did that, but it looks like we only look at the > first char in the decomposition. Yes.