From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Stop frames stealing eachothers' minibuffers! Date: Wed, 06 Jan 2021 09:40:36 +0000 Message-ID: References: <0d14bfc4-8e8e-d3b9-e0e1-ee4bf2e6449d@gmx.at> <20201125210947.GB8228@ACM> <50c96c83-01b4-d2b8-ff90-82c9d706e268@gmx.at> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32150"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Alan Mackenzie , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 06 10:42:11 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 1kx5KV-0008GS-Ek for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Jan 2021 10:42:11 +0100 Original-Received: from localhost ([::1]:51626 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kx5KU-0004nx-Fi for ged-emacs-devel@m.gmane-mx.org; Wed, 06 Jan 2021 04:42:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44996) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kx5J8-000490-GX for emacs-devel@gnu.org; Wed, 06 Jan 2021 04:40:46 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:51178) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kx5J6-00018B-Db for emacs-devel@gnu.org; Wed, 06 Jan 2021 04:40:46 -0500 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 1069edZI007709 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 6 Jan 2021 09:40:39 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 1069fGpL014317; Wed, 6 Jan 2021 09:41:16 GMT In-Reply-To: Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:262581 Archived-At: >> The old behavior is indeed valuable, if only because it is an old >> behavior. Emacs' stability is important. I don't see why the burden of >> proof that a behavior about which virtually no Emacs user in the last >> twenty years complained is not a bad one would be on me. > > M-x lisp-date-mode RET > > signaled an error in all Emacsen until now. Yet no user complained about > it over all these years. Should we add a config var so users can get > back the old behavior? > I think you meant "lisp-data-mode". I'm not sure you are teasing me, so: (1) The "[No match]" error in earlier Emacsen is clear, there is no reason a user would have complained about it. (2) The likelihood that a user tries to type M-x lisp-data-mode RET when no such mode exists is very, very low compared to the likelihood that a user interacts with the minibuffer. Admittedly the scenario that is being discussed here is more precise than "interacting with the minibuffer", but I did experience the old behavior several times without ever thinking it was a bug, and found it perfectly coherent. And I never tried to type M-x lisp-data-mode RET. (3) The old behavior is in this case very easy to get back AFAICS: (fset 'lisp-data-mode nil).