From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: 29.0.60; keymap-local-set and keymap-global-set became less strict Date: Sat, 04 Feb 2023 23:27:10 -0500 Message-ID: References: <5876987d-2479-f512-5767-218c8c16a909@daniel-mendler.de> <875ycngyji.fsf@gnus.org> <87zg9zvzuc.fsf@gmail.com> <831qna3frm.fsf@gnu.org> <87mt5yogct.fsf@gmail.com> <83y1pi1wz4.fsf@gnu.org> <87ilgmodk4.fsf@gmail.com> <83mt5y1r5u.fsf@gnu.org> <87bkmdo8e4.fsf@gmail.com> <831qn91qo0.fsf@gnu.org> <137753af-777d-2da3-c111-7e2d414633f1@daniel-mendler.de> <83sffpze9h.fsf@gnu.org> <309dee07-e404-4f84-a839-8b99815376f8@daniel-mendler.de> <83mt5xz42d.fsf@gnu.org> <83mt5vuewj.fsf@gnu.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3378"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mail@daniel-mendler.de, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Feb 05 05:28:09 2023 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 1pOWdN-0000eT-9Y for ged-emacs-devel@m.gmane-mx.org; Sun, 05 Feb 2023 05:28:09 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pOWcU-0005pJ-Fr; Sat, 04 Feb 2023 23:27:14 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pOWcT-0005ov-3E for emacs-devel@gnu.org; Sat, 04 Feb 2023 23:27:13 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pOWcS-0005QZ-1X; Sat, 04 Feb 2023 23:27:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=HH2aupbdevrsL9TMtLdKdLxC07CSkIjjWdRXUCpQI7k=; b=LtjtjorM3s+v A4yB+JEBHZF6pFzpdhaKu1Vuzp5SVez0kL56ARzPAENYG/tgmonMmH2I5blkmJdGYJZYsrSopVpHx aHeRdYfT8mbXoMNB9njZdG6La6vor0p5vCzHYtaZpyAlStpp2lnzsHcP6gmjti21KybKo5ItoY73Q 2oFrPQGH0JcxCnRFiNsWdwS3G4HHvm4i3Uoi9Fg+IHk+qr0sGrvM3f3VqEoPTRbnAHCu8rP4U2raj ClBXkhJwwRsUW333V6W4NkBMRSg6NvA3bFh9T7Ng7WWzgcVfdMJ8yO2AJq0rL393yR62KySz9O1KL S9UTy80b1m3X2w2dst7W3A==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1pOWcQ-0008JZ-R2; Sat, 04 Feb 2023 23:27:10 -0500 In-Reply-To: <83mt5vuewj.fsf@gnu.org> (message from Eli Zaretskii on Fri, 03 Feb 2023 14:11:56 +0200) 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302990 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > > The advertised API wouldn't change. We don't expect anyone to use the > > > additional argument in non-interactive invocation. We can use > > > advertised-calling-convention declaration to hide that argument from > > > documented interfaces. > > > > Why hide it? It's better to document it. > > Occasionally, passing a nontrivial value for that argument is useful. > We don't want Lisp programs to call this function pretending to be the > user, because this function's raison d'être is to catch invalid key > sequences. I thought we were talking about the general question, comparing various nethods for distinguishing an interactive call. You seem to be talking about why some specific function wants to know when it is called interactively. But I don't know which function it is. In general, when a function does something different for an interactive call. it may be useful for its caller to say, "Treat this call as interactive." For instance, if `foo' does something special if called interactively, and `bar' calls `foo', maybe `bar' wants to check for an interactive call and pass that along to `foo'. With an argument to distinguish, that is eas for `foo' to do. With `callsd-interactiely-p', it seems impossible. -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)