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: Current mode command discovery Date: Wed, 17 Feb 2021 21:25:19 +0200 Message-ID: <835z2q7azk.fsf@gnu.org> References: <87v9aubm96.fsf@gnus.org> <83a6s6bkrg.fsf@gnu.org> <87mtw6bkjo.fsf@gnus.org> <838s7qbjn2.fsf@gnu.org> <87eehi820x.fsf@gnus.org> <83v9at9xel.fsf@gnu.org> <87wnv8xlqa.fsf@gnus.org> <838s7o9g90.fsf@gnu.org> <87im6revhq.fsf@tcd.ie> <83im6r98qd.fsf@gnu.org> <87k0r7uade.fsf@gnus.org> <83eehf978r.fsf@gnu.org> <87ft1vu9hd.fsf@gnus.org> <838s7n95pf.fsf@gnu.org> <8735xvu7sx.fsf@gnus.org> <834kib94ha.fsf@gnu.org> <874kibh9mu.fsf@telefonica.net> <83o8gi7lh2.fsf@gnu.org> <87o8gi37pl.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10953"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ofv@wanadoo.es, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Feb 17 20:26:15 2021 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 1lCSSj-0002iv-Rw for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Feb 2021 20:26:13 +0100 Original-Received: from localhost ([::1]:48470 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCSSi-0002Jp-TG for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Feb 2021 14:26:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46954) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lCSRn-0001r7-Jl for emacs-devel@gnu.org; Wed, 17 Feb 2021 14:25:15 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:53303) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lCSRm-0007pR-Nr; Wed, 17 Feb 2021 14:25:14 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1896 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lCSRh-00029z-6X; Wed, 17 Feb 2021 14:25:12 -0500 In-Reply-To: <87o8gi37pl.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 17 Feb 2021 18:49:42 +0100) 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:265054 Archived-At: > From: Lars Ingebrigtsen > Date: Wed, 17 Feb 2021 18:49:42 +0100 > Cc: Óscar Fuentes , emacs-devel@gnu.org > > Eli Zaretskii writes: > > > Because whoever marked it "nonsensical" made a mistake? Or because > > time passed, things have changed, and what made no sense back then may > > make sense now, and Emacs maintainers missed that or couldn't keep up? > > > > IOW, let's not assume that the marking is perfect. It's done by us, > > and we can make mistakes. > > Any code can have bugs. That doesn't stop us from writing code or > designing systems. > > If there's a bug, we fix the bug. What do you tell a user who cannot invoke a command? "Wait for the next release"? That's why "fire escapes" are useful: they are Plan B for when the unexpected strikes. > But it's extremely unlikely that the tagging of, say, `eww-readable' > will change. Unexpected problems are always unexpected, they cannot be known in advance. Therefore, examples don't help, because examples always talk about something we considered and made a decision about. Whereas "fire escapes" are about risk management, not about design.