[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: |
Sat, 19 Aug 2023 09:34:45 +0300 |
> Date: Sat, 19 Aug 2023 05:05:41 +0000
> From: Heime <heimeborgia@protonmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, "65348@debbugs.gnu.org"
> <65348@debbugs.gnu.org>
>
> > 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.
>
> Eli, would there be some capability to improve the aforementioned
> function from the merits held by the discussion that is happening ?
You can try starting a discussion on emacs-devel if you want. But the
above-mentioned change was not done arbitrarily, and does have its
merit in many situations, so be prepared for hearing people who think
they like the current situation and object to changing it. Drew's
opinion on this are not new, and have been heard (and rejected)
before.
- 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, Heime, 2023/08/18
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/18
- 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
- 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, Heime, 2023/08/18
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/19
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Heime, 2023/08/19
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/19
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Heime, 2023/08/19
- 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, Drew Adams, 2023/08/19
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Eli Zaretskii, 2023/08/19
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/19
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Juri Linkov, 2023/08/20
- bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively, Drew Adams, 2023/08/20
- 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