From: Jean Louis <bugs@gnu.support>
To: Drew Adams <drew.adams@oracle.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: [External] : Doc of deprecated INITIAL-INPUT arg of completing-read
Date: Tue, 28 Jun 2022 22:17:47 +0300 [thread overview]
Message-ID: <YrtT2yG3H9wGEYp3@protected.localdomain> (raw)
In-Reply-To: <SJ0PR10MB5488D0159B15A2C6B08A29FAF3B99@SJ0PR10MB5488.namprd10.prod.outlook.com>
* Drew Adams <drew.adams@oracle.com> [2022-06-27 19:40]:
> There's zero reason to discourage its use in any
> blanket way, let alone "strongly" discourage.
I did not see your message. You said it better, I agree with that
statement.
> INIT and DEF are different in behavior, and thus
> in use cases. Telling users to use one of them
> _instead of_ the other is misguided, IMO.
Exactly.
> All that's needed is to make clear that INIT
> isn't intended as a _substitute_ for a default
> value - and vice versa. That's really the point
> (IMO). The use cases of INIT are different from
> those of DEF. That's what should be made clear.
> Then leave it up to coders to use each as they
> see fit.
That is right, that is where misunderstanding come from.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-06-28 19:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 15:22 Doc of deprecated INITIAL-INPUT arg of completing-read Michael Heerdegen
2022-06-27 16:33 ` [External] : " Drew Adams
2022-06-27 17:22 ` Christopher Dimech
2022-06-28 16:19 ` Michael Heerdegen
2022-06-28 16:40 ` Drew Adams
2022-06-29 13:42 ` Michael Heerdegen
2022-06-29 14:24 ` Drew Adams
2022-06-28 21:46 ` Christopher Dimech
2022-06-29 9:15 ` Arash Esbati
2022-06-29 13:46 ` Michael Heerdegen
2022-06-30 9:10 ` Arash Esbati
2022-07-04 12:25 ` Michael Heerdegen
2022-06-28 19:17 ` Jean Louis [this message]
2022-06-28 19:15 ` Jean Louis
2022-06-28 21:10 ` Stefan Monnier
2022-06-28 22:00 ` Jean Louis
2022-06-29 2:58 ` Stefan Monnier
2022-06-30 3:08 ` Richard Stallman
2022-06-30 14:28 ` Stefan Monnier
2024-02-13 14:43 ` Tim Landscheidt
2024-02-13 14:59 ` Stefan Monnier
2024-02-13 17:07 ` Tim Landscheidt
2024-02-13 20:09 ` Stefan Monnier
2024-02-15 8:21 ` Tim Landscheidt
2024-02-15 16:09 ` [External] : " Drew Adams
2024-02-15 18:39 ` Stefan Monnier
2024-02-17 17:12 ` Tim Landscheidt
2024-02-17 17:41 ` Stefan Monnier
2022-06-30 3:08 ` Richard Stallman
2022-07-01 5:54 ` Jean Louis
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=YrtT2yG3H9wGEYp3@protected.localdomain \
--to=bugs@gnu.support \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).