From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"65348@debbugs.gnu.org" <65348@debbugs.gnu.org>
Subject: bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively
Date: Fri, 18 Aug 2023 19:45:10 +0000 [thread overview]
Message-ID: <2VHlRj-PHCM7ic4tUDOKedNqWt0C9Tu__d2PLGwLt8AZKCRFocxSb-sbTSbwz3aQv3bNv-cPNYxcZsc27bhGpB3jW9eKGDd3v0tvg8v_LJU=@protonmail.com> (raw)
In-Reply-To: <SJ0PR10MB54884F19E158DD529299E9B5F31BA@SJ0PR10MB5488.namprd10.prod.outlook.com>
Sent with Proton Mail secure email.
------- Original Message -------
On Saturday, August 19th, 2023 at 5:33 AM, Drew Adams <drew.adams@oracle.com> wrote:
> > > > The introduction of HIST is only making a good
> > > > function quite terrible to use, becoming an
> > > > over-engineering piece of junk to avoid.
> > >
> > > Useless to claim, without saying why you think so.
> > > And you're quite wrong here, FWIW. HIST is your
> > > friend.
> >
> > 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.
>
> Everyone is different.
Fine. But I cannot see the reason to forced mo to override the value of
'minibuffer-default-add-function' with a function of my own.
Would that not change the way that completing-read works for all my emacs
sessions ? How about having a different function with functionality that
supports the old functionality. There will be the simpler version, and a
more complicated one should people need it. I cannot see how adding the
new functionality means scrapping the legitimate way that I was using it.
> 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.
>
> This is why we have keys such as `M-r' and` M-s'
> that find things in the history.
>
> 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.)
>
> 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.
>
> 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.
>
> > > 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.
> >
> > 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.
>
>
> 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.
>
> 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.
next prev parent reply other threads:[~2023-08-18 19:45 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 0:47 bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 5:49 ` Eli Zaretskii
2023-08-17 6:05 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 7:20 ` Eli Zaretskii
2023-08-17 10:27 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-17 10:45 ` Eli Zaretskii
2023-08-18 0:35 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 1:47 ` Drew Adams
2023-08-18 3:49 ` Eli Zaretskii
2023-08-18 5:13 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 5:36 ` Eli Zaretskii
2023-08-18 5:56 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 6:32 ` Eli Zaretskii
2023-08-18 8:40 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 12:14 ` Eli Zaretskii
2023-08-18 12:27 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 12:30 ` Eli Zaretskii
2023-08-18 12:55 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 13:27 ` Eli Zaretskii
2023-08-18 13:36 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 15:23 ` Drew Adams
2023-08-18 15:16 ` Drew Adams
2023-08-18 15:43 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 17:33 ` Drew Adams
2023-08-18 19:12 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 21:03 ` Drew Adams
2023-08-19 1:55 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 2:34 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 4:14 ` Drew Adams
2023-08-19 4:22 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 4:46 ` Drew Adams
2023-08-19 5:05 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 6:34 ` Eli Zaretskii
2023-08-19 16:20 ` Drew Adams
2023-08-19 19:19 ` Eli Zaretskii
2023-08-19 20:56 ` Drew Adams
2023-08-20 16:39 ` Juri Linkov
2023-08-21 0:23 ` Drew Adams
2023-08-21 4:34 ` Christopher Dimech
2023-08-20 5:42 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 6:12 ` Michael Heerdegen
2023-08-20 6:23 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-20 6:34 ` Christopher Dimech
2023-08-21 0:25 ` Drew Adams
2023-08-21 4:26 ` bug#65348: RE: [External] : " Christopher Dimech
2023-08-21 5:23 ` Drew Adams
2023-08-21 6:29 ` Christopher Dimech
2023-08-21 7:21 ` bug#65348: " Christopher Dimech
2023-08-21 11:40 ` Eli Zaretskii
2023-08-21 12:07 ` Christopher Dimech
2023-08-21 12:25 ` Eli Zaretskii
2023-08-21 13:27 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-21 16:08 ` Drew Adams
2023-08-18 19:45 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-18 21:07 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='2VHlRj-PHCM7ic4tUDOKedNqWt0C9Tu__d2PLGwLt8AZKCRFocxSb-sbTSbwz3aQv3bNv-cPNYxcZsc27bhGpB3jW9eKGDd3v0tvg8v_LJU=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=65348@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).