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: Thu, 01 Sep 2022 10:14:55 +0200 Message-ID: <87r10vik8w.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> <86o7w2196j.fsf@mail.linkov.net> <87mtbkkdb5.fsf@gmail.com> <867d2ol9yl.fsf@mail.linkov.net> <861qsvef9w.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16118"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier , Eli Zaretskii , emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 01 11:30:54 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 1oTgXG-00041Q-CE for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Sep 2022 11:30:54 +0200 Original-Received: from localhost ([::1]:56868 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oTgXF-0000Ao-2B for ged-emacs-devel@m.gmane-mx.org; Thu, 01 Sep 2022 05:30:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60360) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oTfLp-0001eQ-Hs for emacs-devel@gnu.org; Thu, 01 Sep 2022 04:15:01 -0400 Original-Received: from mail-wr1-x42c.google.com ([2a00:1450:4864:20::42c]:42725) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oTfLn-00078C-IG; Thu, 01 Sep 2022 04:15:00 -0400 Original-Received: by mail-wr1-x42c.google.com with SMTP id m16so21229937wru.9; Thu, 01 Sep 2022 01:14:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:from:to:cc:subject:date; bh=gfVv3KMgQptCvj0qv0Jh2+G/Y6/e01P+IAsnaJpl8wM=; b=OXwOWIfs79b0AktO4/B2eLXH9KsM7kfFZ65MQ16si7qr7fhcLJUpddpnjU7dNqfUZB HDtDgpdaJVCfmQxt6C2pr8g/FDUwnMCFQkuOb0ssB1DMJan8QmumLg0IlFUeRp6QyTOW e76BJlR9ZMTIb3GHi5b1yhdluZEDwUCjROGp69ifxsoVqiB/5ZFMu6EXkydU1PMqRiRM 27rd5E+gR5tCN/qxL0PHzJdmA6YJhE8hHHAPAkWTnm2jG7PxPohjWk/LENfHUrYoK1RI 5bvsubZGo297XlHJZxRtRx+NJ3LMbE20b20zrMw1Q0l/t1M78hCOghAGTLENWHmwAZNg dyKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date; bh=gfVv3KMgQptCvj0qv0Jh2+G/Y6/e01P+IAsnaJpl8wM=; b=MO59Ie6K56Y5ayVb/m2JU/Jy+v58ampNWqtuuQExviL334rrqB7ZtpesDTtAyyKvcT oXae9LzVpfT6gG9F68SwZ3oSd6BMOR/dcknUJDsriOxvMcHhwaXIRyGyJfsNMAzUNhs1 E7uRJ8PN0iXhRj2oDyTz9p6KgcGlJviaE56giCKjtP/kedFKHKIiuwb2nJnBC2ZqE54w AyRCqVcXO7KEszS3x54yRvXmsaXEkj5Y1sGtEfh8v6OVBii5sl01TNlDfJH4tHUcYDIG fLXhXVhn3orYz+NpDRP1AMDBBm0zj6upWKlrruEYYkl8SSBo+4vwvE2XpQ65QZrQGDwg FvZA== X-Gm-Message-State: ACgBeo2nDH2GXu3BO94hZ6/KOEVZ5uOB6ShcbIVFUc4h7nM/F7lUAZYi DOsb6koZq0BOZcQqFUGcP2KpIb9AIKg= X-Google-Smtp-Source: AA6agR6BIP81ZrPCLGldn1Hwb/00OH9O9Ratw82MTuhInbZ17LnkBsHHo1ntbnnQK5hosr3B7gNIpw== X-Received: by 2002:adf:eb0e:0:b0:226:db7d:6fed with SMTP id s14-20020adfeb0e000000b00226db7d6fedmr10316272wrn.626.1662020097018; Thu, 01 Sep 2022 01:14:57 -0700 (PDT) Original-Received: from rltb ([2a01:e0a:3f3:fb50:34fb:6aed:1aac:5cee]) by smtp.gmail.com with ESMTPSA id da12-20020a056000408c00b0021ee65426a2sm15135132wrb.65.2022.09.01.01.14.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Sep 2022 01:14:56 -0700 (PDT) In-Reply-To: <861qsvef9w.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 01 Sep 2022 10:22:55 +0300") Received-SPF: pass client-ip=2a00:1450:4864:20::42c; envelope-from=rpluim@gmail.com; helo=mail-wr1-x42c.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:294471 Archived-At: >>>>> On Thu, 01 Sep 2022 10:22:55 +0300, Juri Linkov sai= d: >>>> I have one comment: using `read-char-by-name' is kind >>>> of cumbersome when all you want to do is find the equivalents to >>>> e.g. 'a'. Would it make sense to have something similar to >>>> `read-char-by-name' but that accepted single characters *without* >>>> treating those as hex? You=CA=BCd still be able to enter single di= git >>>> hex characters by prefixing them with '0'. >>> Wouldn't it be cleaner to use just (read-char-from-minibuffer "Char= acter: ") >>> where you can either type a character directly or use 'C-x 8 RET' >>> to insert a character by its name. >>=20 >> I lost the beginning of this discussion: why can't we unify >> `read-char-from-minibuffer` and `read-char-by-name' into a single fu= nction? Juri> Robert sent a patch that does this by adding a new arg ALLOW-SING= LE Juri> to `read-char-by-name'. You still need to hit RET though, unlike `read-char-from-minibuffer'. Robert --=20