From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: [External] : Doc of deprecated INITIAL-INPUT arg of completing-read Date: Tue, 28 Jun 2022 22:17:47 +0300 Message-ID: References: <87v8smt9lp.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39680"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/+ () (2022-05-21) Cc: Michael Heerdegen , Emacs Development To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jun 28 21:25:03 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o6Gpb-000A7A-4Q for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Jun 2022 21:25:03 +0200 Original-Received: from localhost ([::1]:45738 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o6GpZ-0008DD-N6 for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Jun 2022 15:25:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48870) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6GoG-0006Iq-75 for emacs-devel@gnu.org; Tue, 28 Jun 2022 15:23:40 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:35629) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6GoD-0000wz-PF for emacs-devel@gnu.org; Tue, 28 Jun 2022 15:23:39 -0400 Original-Received: from localhost ([::ffff:197.239.7.68]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000087C50.0000000062BB5538.00006F21; Tue, 28 Jun 2022 12:23:35 -0700 Mail-Followup-To: Drew Adams , Michael Heerdegen , Emacs Development Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SBL=0.141, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291698 Archived-At: * Drew Adams [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/