From: Christopher Dimech <dimech@gmx.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Emanuel Berg <incal@dataswamp.org>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: RE: [External] : completing-read depricated initial-input
Date: Fri, 24 Jun 2022 21:33:16 +0200 [thread overview]
Message-ID: <trinity-8bc51a21-c8c2-4903-a9ee-c5afb3a75082-1656099196215@3c-app-mailcom-bs13> (raw)
In-Reply-To: <SJ0PR10MB5488067EA60180903D615CA9F3B49@SJ0PR10MB5488.namprd10.prod.outlook.com>
> Sent: Saturday, June 25, 2022 at 2:30 AM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Emanuel Berg" <incal@dataswamp.org>, "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
> Subject: RE: [External] : Re: completing-read depricated initial-input
>
> > I already asked, what concept is the initial value?
> ...
> > "Why is the computer putting stuff there? It's
> > the area where the human user should put stuff."
> ...
> > There is only one use case (completion with a
> > common prefix)
>
> Please read (again?) what others have written.
>
> First, it's initial _input_, not initial value. It's
> about prefilling the minibuffer with particular text,
> which you can use any way you like (e.g. edit it).
>
> A common prefix is only one such use case. (For one
> thing, prefix completion isn't all there is nowadays.)
>
> As the arg to `completing-read', `read-from-minibuffer',
> `read-string', `read-buffer', `read-minibuffer', etc.,
> it's unrelated to any default value. (More precisely,
> it's not _necessarily_ related.)
>
> There's no reason it shouldn't be possible to provide
> you an initial-input that's useful for editing, even
> one that might not be directly related to any default
> value.
> ___
>
> As for inserting the _default value_ (not the INIT arg)
> in the minibuffer automatically: a user might want that.
> You might not; others might. This should be a user
> choice, not imposed one way or the other.
>
> As I said:
>
> If you often want to use or edit the default value,
> then consider setting `icicle-default-value' to
> non-`nil' and non-`t' [to insert it in the minibuffer].
>
> If you rarely do so, then consider using `nil' or `t'
> [to not insert it].
>
> As one user, I'm in the former camp: I often want
> to use or edit the default value, and as a result I
> prefer that it be inserted automatically.
>
> That is, I prefer to hit a key to delete it, in the
> (fewer) cases where I don't want it, than to have to
> hit `M-n' to insert it, in the (more numerous) cases
> where I do want it (including to edit it, rather
> than just accept it as is).
>
> Remember that minibuffer reading is not always, or
> even usually, a must-match situation. Even for
> completion, there's lax completion (REQUIRE-MATCH
> nil).
>
> With well-designed code a `completing-read' call
> with lax completion can nevertheless provide a
> helpful default value - e.g., one that I might want
> to edit slightly.
>
> Of course, a `completing-read' call that gives you
> a poor default value lessens the utility of using
> it, and so lessens the usefulness of inserting it.
>
> Again, this want-or-don't-want-DEF-inserted is akin
> to whether to use `delete-selection-mode'. I do
> use that mode. Users are different.
>
> And it's important, IMO, to have a single key to
> empty the minibuffer, regardless of where point is.
> In `icy-mode' that's `M-k', by default. Vanilla
> Emacs still has no such key. (Why not?)
>
> Neither (1) having to use `M-n' to insert the
> default, nor (2) having to use `M-k' to erase its
> automatic insertion, is super bothersome. Each
> can make sense and be preferred by some users.
> That's all.
> ___
>
> Summary:
>
> 1. There are uses for an initial-input arg.
> 2. Automatic insertion of the default value can
> be useful and preferred by some users. Let
> users choose.
> 3. Emacs shouldn't deprecate, let alone get rid
> of, an initial-input arg for `completing-read'.
> In fact, it should consider adding one for
> some functions that don't have it - some of
> the `read-*' functions, for example.
I fully support the summary as well.
next prev parent reply other threads:[~2022-06-24 19:33 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 7:56 completing-read depricated initial-input carlmarcos--- via Users list for the GNU Emacs text editor
[not found] ` <N54Fw5q--3-2@tutanota.com-N54INof----2>
2022-06-21 9:51 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-21 11:19 ` Michael Heerdegen
2022-06-21 12:39 ` Emanuel Berg
2022-06-21 12:46 ` Michael Heerdegen
2022-06-21 14:04 ` [External] : " Drew Adams
2022-06-21 14:10 ` Michael Heerdegen
2022-06-21 14:49 ` Drew Adams
2022-06-22 8:50 ` Jean Louis
2022-06-22 9:32 ` Emanuel Berg
2022-06-21 10:26 ` Robert Pluim
2022-06-21 11:15 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-21 12:39 ` Christopher Dimech
2022-06-21 14:09 ` [External] : " Drew Adams
2022-06-21 18:21 ` Arash Esbati
2022-06-21 19:04 ` Emanuel Berg
2022-06-21 20:41 ` [External] : " Drew Adams
2022-06-21 21:28 ` Arash Esbati
2022-06-21 22:07 ` [External] : " Drew Adams
2022-06-21 22:56 ` Emanuel Berg
2022-06-22 13:43 ` Drew Adams
2022-06-22 15:59 ` standard libraries again (was: Re: [External] : Re: completing-read depricated initial-input) Emanuel Berg
2022-06-22 17:39 ` Drew Adams
2022-06-22 18:05 ` Emanuel Berg
2022-06-22 20:53 ` Drew Adams
2022-06-22 21:18 ` Emanuel Berg
2022-06-23 7:59 ` completing-read depricated initial-input Arash Esbati
2022-06-23 10:06 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-23 20:57 ` Emanuel Berg
2022-06-23 11:19 ` Michael Heerdegen
2022-06-23 12:12 ` Arash Esbati
2022-06-23 14:52 ` Michael Heerdegen
2022-06-23 16:30 ` [External] : " Drew Adams
2022-06-23 16:41 ` Michael Heerdegen
2022-06-23 18:27 ` Christopher Dimech
2022-06-23 21:14 ` Emanuel Berg
2022-06-23 18:25 ` RE: [External] : " Christopher Dimech
2022-06-23 21:13 ` [External] : " Emanuel Berg
2022-06-23 21:07 ` Emanuel Berg
2022-06-23 21:06 ` Emanuel Berg
2022-06-23 14:36 ` Jean Louis
2022-06-24 2:35 ` Emanuel Berg
2022-06-24 6:59 ` Jean Louis
2022-06-23 15:19 ` Jean Louis
2022-06-23 15:24 ` Jean Louis
2022-06-23 21:05 ` Stefan Monnier
2022-06-23 22:10 ` Christopher Dimech
2022-06-23 22:19 ` Stefan Monnier
2022-06-23 22:28 ` Christopher Dimech
2022-06-24 7:08 ` Jean Louis
2022-06-24 8:19 ` Christopher Dimech
2022-06-24 11:00 ` Jean Louis
2022-06-24 16:58 ` Christopher Dimech
2022-06-24 8:19 ` Emanuel Berg
2022-06-24 11:31 ` Jean Louis
2022-06-25 18:54 ` Emanuel Berg
2022-06-25 19:51 ` Jean Louis
2022-06-26 17:36 ` Emanuel Berg
2022-06-24 14:30 ` [External] : " Drew Adams
2022-06-24 19:33 ` Christopher Dimech [this message]
2022-06-25 19:12 ` Emanuel Berg
2022-06-25 21:26 ` Drew Adams
2022-06-26 17:39 ` Emanuel Berg
2022-06-26 22:22 ` Drew Adams
2022-06-26 22:42 ` Emanuel Berg
2022-06-24 0:10 ` Drew Adams
2022-06-24 8:09 ` RE: [External] : " Christopher Dimech
2022-06-24 2:29 ` Emanuel Berg
2022-06-23 16:23 ` [External] : " Drew Adams
2022-06-23 20:58 ` Arash Esbati
2022-06-23 21:54 ` Christopher Dimech
2022-06-24 2:49 ` Emanuel Berg
2022-06-22 3:09 ` Po Lu
2022-06-22 3:46 ` Emanuel Berg
2022-06-22 4:56 ` Christopher Dimech
2022-06-23 8:20 ` Arash Esbati
2022-06-23 8:27 ` Emanuel Berg
2022-06-23 8:57 ` Tassilo Horn
2022-06-23 10:10 ` Emanuel Berg
2022-06-23 11:26 ` Tassilo Horn
2022-06-23 11:48 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-23 21:38 ` Emanuel Berg
2022-06-24 8:03 ` Christopher Dimech
2022-06-23 21:34 ` Emanuel Berg
2022-06-23 11:58 ` Arash Esbati
2022-06-23 12:10 ` Lars Ingebrigtsen
2022-06-23 14:26 ` Tassilo Horn
2022-06-23 14:46 ` Arash Esbati
2022-06-23 15:18 ` Robert Pluim
2022-06-23 20:46 ` Arash Esbati
2022-06-24 8:40 ` Philip Kaludercic
2022-06-24 2:22 ` Emanuel Berg
2022-06-24 2:17 ` Emanuel Berg
2022-06-23 21:49 ` Emanuel Berg
2022-06-23 21:42 ` Emanuel Berg
2022-06-23 16:25 ` [External] : " Drew Adams
2022-06-23 19:56 ` Tassilo Horn
2022-06-24 11:23 ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-06-24 11:36 ` Jean Louis
2022-06-25 19:01 ` Emanuel Berg
2022-06-25 21:26 ` Drew Adams
2022-06-22 2:59 ` RE: [External] : " Christopher Dimech
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-8bc51a21-c8c2-4903-a9ee-c5afb3a75082-1656099196215@3c-app-mailcom-bs13 \
--to=dimech@gmx.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).