[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: completing-read depricated initial-input

From: Jean Louis
Subject: Re: completing-read depricated initial-input
Date: Fri, 24 Jun 2022 14:31:35 +0300
User-agent: Mutt/+ () (2022-05-21)

* Emanuel Berg <> [2022-06-24 11:26]:
> Jean Louis wrote:
> > (read-from-minibuffer "Your name: " nil nil nil nil "Jean")
> Holy cow, there's no need to hard code that! What if you were
> to change your name (nom de guerre if you wish) for romantic
> and/or conspiratorial reasons? Use `user-full-name'
> instead ...

Which name? That is not name, that is:

1. jean, blue jean, denim -- ((usually plural) close-fitting trousers of heavy 
denim for manual work or casual wear)

Jokes aside... 👁️

> >> Inserting default would make sense. We should not continue
> >> with the initial-value name then. Stating that DEF will be
> >> displayed as first instance. Making things smoother and
> >> clearer to understand.
> >
> > I do not find it so. I do not say how function works, but
> > I wish to say what I expect as user.
> We have been thinking of it in very practical terms so far.
> I already asked, what concept is the initial value? I'm not
> aware of any such concept in this context. One can think of
> several UIs (including GUIs) where the initial value has been
> inserted to communicate the default value, and enable -
> transparently, even - for the user to submit this value.
> In that sense, it isn't that bad: the default value is shown
> loud and clear, it can be edited and when its submitted this
> happens with the same method so no extras in terms of
> technology at that end.

It is my sincere hope you will understand the difference between those

1) Default is what will be chosen if use press enter, regardless if
   user sees that default or not. That is my expectation, but
   read-from-minibuffer in development version does not behave this

   Personally I have heavy uses of defaults, such as "Default address"
   while some addresses are rather different "Work address" or
   "Temporary address". I need default address, thus it is usable for

2) Initial value is usable as it is visible and makes it easier to
   make the choice, but it is not necessarily default.

   My personal example is that some people have one address in
   Germany, other in Austria, but one of those addresses is default
   (this word now has no relation to Emacs). If letter has been sent
   last 2 times to Austria, system can recognize it and offer such as
   initial input. But if Austria is not choosen, or if nothing in
   particular has been seen in the prompt and user hits RET, then
   default German address would be choosen.

   Another example is that I am entering phone numbers every
   day. Communication line is "Phone" but type is "Default", which
   means nothing in particular. However, I start entering many mobile
   numbers, than I appreciate that system looks in past and offers me
   "Mobile" as initial input, just to press enter, while my Default
   would be choosen if I delete it and press enter on empty

   │ Addreses in last year │ Count  │
   │ Addresses             │ 197299 │

   The above personal example I go through many times per day.

   In my example I do not use initial-value to communicate default,
   but to communicate the choice which could be more probable based on
   last information. That choice may be dynamically chosen, it is not
   hard code.


Take action in Free Software Foundation campaigns:

In support of Richard M. Stallman

reply via email to

[Prev in Thread] Current Thread [Next in Thread]