From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively Date: Fri, 18 Aug 2023 19:12:49 +0000 Message-ID: References: <83msyq54mw.fsf@gnu.org> <6lEyA2hwLwT0gnrhQsH91Us8wQDf0Cj8-hfYtge1iLDBFEsG5Hj_i80te8w4f52fgOS-g9Z908HRkYHlE05wBV9ccB5h1bFjV755l9nvYh0=@protonmail.com> <83y1i93t7x.fsf@gnu.org> Reply-To: Heime 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="35279"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , "65348@debbugs.gnu.org" <65348@debbugs.gnu.org> To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Aug 18 21:14:24 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1qX4vQ-000906-B0 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 18 Aug 2023 21:14:24 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qX4v5-0003Q5-Di; Fri, 18 Aug 2023 15:14:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qX4v3-0003Pn-HI for bug-gnu-emacs@gnu.org; Fri, 18 Aug 2023 15:14:01 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qX4v3-0007Ex-9x for bug-gnu-emacs@gnu.org; Fri, 18 Aug 2023 15:14:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qX4v3-0004h1-NR for bug-gnu-emacs@gnu.org; Fri, 18 Aug 2023 15:14:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Heime Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 18 Aug 2023 19:14:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65348 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 65348-submit@debbugs.gnu.org id=B65348.169238599417968 (code B ref 65348); Fri, 18 Aug 2023 19:14:01 +0000 Original-Received: (at 65348) by debbugs.gnu.org; 18 Aug 2023 19:13:14 +0000 Original-Received: from localhost ([127.0.0.1]:48822 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qX4uI-0004fk-Ap for submit@debbugs.gnu.org; Fri, 18 Aug 2023 15:13:14 -0400 Original-Received: from mail-40132.protonmail.ch ([185.70.40.132]:60107) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qX4uG-0004fQ-Od for 65348@debbugs.gnu.org; Fri, 18 Aug 2023 15:13:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1692385985; x=1692645185; bh=svzQEZRBwTOOQOgikrdWRigWwAS3g/YVq4JlZvd0BY4=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=rf7HyAAl4jLPQv08/yGpYJvIvSYY0fcmXtdFJ5bztpNs+I9MgNk21GWu6fwGKmIvN nsYtaBBdCUAW6dAqs/atcKMLBNV3/P+SQtTi0vZ/4CsgmMmcV2/AmQNXqNZABarzhW Az37/8fRAcPCutXEHO3QRBqyZyLD/OxBwIpbnsSvVS0NP5dm12y5lgFoMl2f9O9CHz XhZ95PcILQk7senaLZW4Xq3QjD5huJX9FHCvCnvdYU2HGCWk4t26AK6YwA8mRUwYTp PlVhkgeUJNmOWxUm2mInvSn9rBGgAyuGCG4sgmEf++/pSaR0wM6wRsnA9bFaLumFbi LlopvHvM6jGvA== In-Reply-To: Feedback-ID: 57735886:user:proton X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:267783 Archived-At: ------- Original Message ------- On Saturday, August 19th, 2023 at 5:33 AM, Drew Adams wrote: > > > > The introduction of HIST is only making a good > > > > function quite terrible to use, becoming an > > > > over-engineering piece of junk to avoid. > > >=20 > > > Useless to claim, without saying why you think so. > > > And you're quite wrong here, FWIW. HIST is your > > > friend. > >=20 > > When using my own function that selects from a collection, I am never > > interested in the history. Just want it to cycle through the entries, > > that's all. And the less things I got to type, the better. >=20 >=20 > Everyone is different. >=20 > But know that cycling is not always an efficient > way to get to something. It can be fine if the > thing you want to get to is close by. It can be > awful if it's far. >=20 > This is why we have keys such as `M-r' and` M-s' > that find things in the history. >=20 > It can also help to have completion against the > history. (If you'd read the page I pointed to > about Icicles history enhancements you'd have > seen more than one possibility for that.) >=20 > Cycling can be helpful for accessing COLLECTION > matches or for accessing history elements. But > cycling is an inherently dumb, inefficient way > to find a needle in a haystack. A magnet works > better than checking each bit of hay in turn. I use completing-read so I do not have to remember=20 collection matches.=20 =20 > Being able to sort completion candidates is one > way to tame dumb cycling. Being able to filter > them is another. It's really important to have > ways to tame a large set of choices, whether > they are completion candidates, input-history > candidates, or anything else. >=20 > > > Callers of `completing-read' can decide whether it > > > makes sense (they think) to insert. And users > > > should be able to override the caller's choice. > >=20 > > It seems that now I have to know all about the HIST things, > > the DEF, the over-riding of same value to call some function > > that I have to write to get the behaviour I was using, etc. >=20 >=20 > You don't have to know anything. And yes, there > are a multitude of things you can learn, to make > your Emacs life easier, more efficient, more > enjoyable, more enlightening. >=20 > Some people use Emacs for a long time without > bothering to learn other ways of doing things > than what they learned the first week. Some use > menus and mouse alone, pretty much. Others get > along better as time goes on, picking up various > ways to do things easier or quicker. Often that > includes writing some code or picking up some > code (e.g. packages) written by others. YMMV.