From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Delete variables obsolete since Emacs 23 Date: Tue, 18 Aug 2020 07:53:12 +0300 Message-ID: <83r1s4ftc7.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30011"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, ghe@sdf.org, drew.adams@oracle.com, stefankangas@gmail.com To: Jeff Norden Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 18 06:54:07 2020 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 1k7tdP-0007cn-05 for ged-emacs-devel@m.gmane-mx.org; Tue, 18 Aug 2020 06:54:07 +0200 Original-Received: from localhost ([::1]:43188 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k7tdO-0000Bo-39 for ged-emacs-devel@m.gmane-mx.org; Tue, 18 Aug 2020 00:54:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57400) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7tcv-0008CS-GJ for emacs-devel@gnu.org; Tue, 18 Aug 2020 00:53:37 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:45490) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k7tcs-0002rn-Pe; Tue, 18 Aug 2020 00:53:34 -0400 Original-Received: from [176.228.60.248] (port=3484 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1k7tcl-0007qT-7D; Tue, 18 Aug 2020 00:53:28 -0400 In-Reply-To: (message from Jeff Norden on Mon, 17 Aug 2020 20:55:56 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:253926 Archived-At: > From: Jeff Norden > Date: Mon, 17 Aug 2020 20:55:56 -0500 > Cc: ghe@sdf.org, stefankangas@gmail.com, rms@gnu.org, monnier@iro.umontreal.ca, > emacs-devel@gnu.org > > The elisp manual says: > > You can mark a named function as "obsolete", meaning that it may be > removed at some point in the future. This causes Emacs to warn that the > function is obsolete whenever it byte-compiles code containing that > function, and whenever it displays the documentation for that function. > In all other respects, an obsolete function behaves like any other > function. > > The phrase "may be removed" seems a bit vague. Would "will be removed" or > "will probably be removed" be more accurate? No, it won't. Primarily because we don't really know whether we will remove it, let alone when. It depends on too many factors that we cannot predict. > The fact that emacs maintains backward compatibility so well is one of the > features that I appreciate the most. But, in this case, the fact that > interactive-p has been obsolete for so long may give the impression that it > would continue to be available. I think the gentle annoyance we have now strikes the right balance between not letting people forget the fact of obsolescence and not annoying them too much. We are talking to adults, not to children, so we can rely on them doing TRT.