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: Heime <heimeborgia <at> protonmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 65348 <at> debbugs.gnu.org
Subject: bug#65348: INITIAL-INPUT in completing-read repeats same entry twice consecutively
Date: Fri, 18 Aug 2023 05:13:46 +0000

Sent with Proton Mail secure email.

------- Original Message -------
On Friday, August 18th, 2023 at 3:49 PM, Eli Zaretskii <eliz <at> gnu.org> wrote:


> > Date: Fri, 18 Aug 2023 00:35:09 +0000
> > From: Heime heimeborgia <at> protonmail.com
> > Cc: 65348 <at> debbugs.gnu.org
> > 
> > So one is not supposed to have the value in COLLECTION if it has been specified
> > in INITIAL ?
> 
> 
> You can have it there. It does work.

But you are designating it as deprecated, which makes others think that something
awful is going to happen to it.  The introduction of HIST is only making a good
function quite terrible to use, becoming an over-engineering piece of junk to avoid.  
 
> > I find using INITIAL quite useful because the user sees something filled up.
> > What is one to do instead ?
> 
> 
> Why do you need INITIAL?

I want the user to see a default without having him to get it with the bloody "M-n".

Having the user yank it from the default to the minibuffer is a bother, not a way to 
make things easier.

Previous Next

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