[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#65348: INITIAL-INPUT in completing-read repeats same entry twice con
From: |
Eli Zaretskii |
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@gmx.com>
> Cc: Michael Heerdegen <michael_heerdegen@web.de>, "65348@debbugs.gnu.org"
> <65348@debbugs.gnu.org>, "heimeborgia@protonmail.com"
> <heimeborgia@protonmail.com>, Drew Adams <drew.adams@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.
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, (continued)
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Christopher Dimech, 2023/08/21
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Heime, 2023/08/20
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Michael Heerdegen, 2023/08/20
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Heime, 2023/08/20
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Christopher Dimech, 2023/08/20
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/20
- bug#65348: RE: [External] : bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Christopher Dimech, 2023/08/21
- bug#65348: RE: [External] : bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/21
- bug#65348: RE: [External] : bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Christopher Dimech, 2023/08/21
- bug#65348: RE: RE: [External] : bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Christopher Dimech, 2023/08/21
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively,
Eli Zaretskii <=
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Christopher Dimech, 2023/08/21
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Eli Zaretskii, 2023/08/21
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Heime, 2023/08/21
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/21
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Heime, 2023/08/18
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/18