GNU bug report logs - #65348
INITIAL-INPUT in completing-read repeats same entry twice consecutively

Previous Next

Full log

Message #105 received at 65348 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Heime <heimeborgia <at> protonmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>,
 "65348 <at> debbugs.gnu.org" <65348 <at> debbugs.gnu.org>
Subject: RE: [External] : Re: bug#65348: INITIAL-INPUT in completing-read
 repeats same entry twice consecutively
Date: Sat, 19 Aug 2023 04:46:56 +0000

> > > Would it not be better to COLLECTION and HISTORY separate ?
> >
> > You already have my opinion: yes. And they always
> > have been, till Someone (TM) decided recently that
> > future history should include all of the candidates
> > in COLLECTION.
> 
> Right.  Because entries in history ought to be stored in history
> as you input values, not before.

Not so, for "future history" (and that's why that cute
term isn't a good one).  The so-called "future history"
is one or more DEFAULT values you can retrieve and use
as input if you like.

After use of DEFAULT (`M-n') got rebaptized as using
"future history", Someone (TM) got the dim idea to add
all of COLLECTION to that list, along with the DEFAULT
values.  DEFAULT values belong, properly, to "future
history" (though that's a misleading misnomer).

But COLLECTION doesn't belong in "future history".
The reason isn't what you gave, though.  It's proper
to fill the "future history" before you choose input,
but it's only proper to fill it with default values.
What's not good is to also fill it with all of the
possible completion choices.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.