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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Christopher Dimech <dimech <at> gmx.com>
Cc: michael_heerdegen <at> web.de, heimeborgia <at> protonmail.com, 65348 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively
Date: Mon, 21 Aug 2023 15:25:46 +0300

> From: Christopher Dimech <dimech <at> gmx.com>
> Cc: michael_heerdegen <at> web.de, 65348 <at> debbugs.gnu.org,
>  heimeborgia <at> protonmail.com, drew.adams <at> oracle.com
> Date: Mon, 21 Aug 2023 14:07:07 +0200
> 
> > There are no plans to remove INITIAL-INPUT, if that's what you are
> > asking.  We cannot possibly remove it, ever.  The argument is not
> > deprecated; its _use_ is "deprecated" (a.k.a. "discouraged"), that's
> > all.
> 
> INITIAL-INPUT is basically meant for prefilling the minibuffer with an entry.

Yes.

> Do not see anything to encourage or discourage.

The doc string and the manual explain this.

> Perhaps renaming it would be more appropriate to describe what
> actually happens ?

I see no reason to rename, as the current name describes the purpose
quite well.

Previous Next

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