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 14:40:17 +0300

> From: Christopher Dimech <dimech <at> gmx.com>
> Cc: Michael Heerdegen <michael_heerdegen <at> web.de>, "65348 <at> debbugs.gnu.org"
>  <65348 <at> debbugs.gnu.org>, "heimeborgia <at> protonmail.com"
>  <heimeborgia <at> protonmail.com>, Drew Adams <drew.adams <at> oracle.com>
> Date: Mon, 21 Aug 2023 09:21:40 +0200
> 
> Eli, there needs to be some clarification.

I think the situation is clear, you (not necessarily you personally)
are just splitting hair and desperately looking for problems where
there are none.

> What is the situation exactly ? Is the use of nil for INITIAL-INPUT
> consistent with the future plan about INITIAL-INPUT ?  Having the ability
> to prefill the minibuffer with a collection entry is perfectly reasonable
> expectation for people to use.

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.

There's no problem here.

Previous Next

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