From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Robert Pluim Newsgroups: gmane.emacs.devel Subject: Re: emacs-28 a866674b2a: Fix inaccuracies in "lax search" documentation Date: Wed, 27 Jul 2022 10:13:20 +0200 Message-ID: <87mtcv55y7.fsf@gmail.com> 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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39689"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 27 10:18:12 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 1oGcFA-000A7V-Bq for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jul 2022 10:18:12 +0200 Original-Received: from localhost ([::1]:34390 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oGcF8-0000Gg-VS for ged-emacs-devel@m.gmane-mx.org; Wed, 27 Jul 2022 04:18:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53996) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGcAX-0004TP-Gd for emacs-devel@gnu.org; Wed, 27 Jul 2022 04:13:25 -0400 Original-Received: from mail-wr1-x432.google.com ([2a00:1450:4864:20::432]:42662) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oGcAW-00082m-0r; Wed, 27 Jul 2022 04:13:25 -0400 Original-Received: by mail-wr1-x432.google.com with SMTP id bn9so12229999wrb.9; Wed, 27 Jul 2022 01:13:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:from:to:cc; bh=5Q+Y4SPgHDrQSmc4qnk6/izrOFxN/xNYNILrFr/qK8M=; b=K994T/PI0uh1I5b6RWksguqlY23YhGfwLG70eSlQ3yMhR+dNE0ZmqgdQE8Wfto0qr5 8sTMYc7Lb8H+tUu57VafBM5bTLywGtylxS3K1IUJzUo515Yp3EPQdZ1D8rhuz2KHlFsg nVoMWgB8MYbz/R+iiqadrj7Fta9h2R9627RXKASBdmCI4Ixn9nw8s7Y1773NBZ2pIIul rJaLuc+deASoUqkNnajoB91KhDGNxn7/ZyNP2wXpcjMdccd9Brqud1jgIz/z159OIS/e 2jB8fSb2UkQjuUXaS5M0myPYdRvz438QEnYihXJQqJmFZmCnYXkc6pko83kY5bikclx6 EEVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:x-gm-message-state:from:to:cc; bh=5Q+Y4SPgHDrQSmc4qnk6/izrOFxN/xNYNILrFr/qK8M=; b=qUuRmRPV2MeQlbV8/2S071PrBTHlMxvhRJH7V1tBEMFsDA4phs3c/kWHZzTm46NF1J YXWJKYxvaawiW2rstiuGVm+ORxe8XFsQUrrLGrWIb44WkNKMSYy2O/dHEXV+zmrISUeV hCRKO7qycto4jJ2jgGUAXlH4bFHA/7EazkmjQRhsjQoKIJ8+yyBJ8s+oDxmB1m4dflt8 onLk2mOHqhzw8whbXdoOdPjORA1Yoh4KVOmQj+YJA6rw34URs7AYURSjQ2H/6zpfQfRV nu50YRjokhJHpXLRWVYz3kehRq2034PbF8dHS1C8FNdyR5w+ObVGx+4zK05bIlPyp0LS Mb4w== X-Gm-Message-State: AJIora+Aj/mQhRC/Sz3TDwst41P90obU1jwuddBKxbDcOVHKBvX2gv+I kvnOME/nqyt383OqsTXbsbBKlhTvZEE= X-Google-Smtp-Source: AGRyM1sLRW/89agNohdDZ+9r5BzmADD/6hgUdgITJnnKbodto9wTK5yB1FCBMzbE9GpLRj4na065jw== X-Received: by 2002:a5d:5222:0:b0:21e:c5af:18af with SMTP id i2-20020a5d5222000000b0021ec5af18afmr1759512wra.102.1658909601584; Wed, 27 Jul 2022 01:13:21 -0700 (PDT) Original-Received: from rltb ([2a01:e0a:3f3:fb50:b05d:deec:a988:4ea3]) by smtp.gmail.com with ESMTPSA id t18-20020a05600c199200b003a3278d5cafsm1526607wmq.28.2022.07.27.01.13.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Jul 2022 01:13:20 -0700 (PDT) In-Reply-To: <867d3z9ewc.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 27 Jul 2022 10:46:27 +0300") Received-SPF: pass client-ip=2a00:1450:4864:20::432; envelope-from=rpluim@gmail.com; helo=mail-wr1-x432.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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:292732 Archived-At: >>>>> 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). Robert --