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.bugs Subject: bug#60859: [PATCH] Remove reference to the kbd function from documentation Date: Mon, 16 Jan 2023 18:56:37 +0200 Message-ID: <83cz7e4dve.fsf@gnu.org> References: <87pmbeivcl.fsf@panoramix.zarniwoop.org> <83ilh64juj.fsf@gnu.org> <87o7qyo3nc.fsf@panoramix.zarniwoop.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37550"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 60859@debbugs.gnu.org To: Panagiotis Koutsourakis Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jan 16 17:57:27 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1pHSnW-0009Ub-2T for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 16 Jan 2023 17:57:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pHSnA-0001YB-9N; Mon, 16 Jan 2023 11:57:04 -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 1pHSn8-0001Xr-TK for bug-gnu-emacs@gnu.org; Mon, 16 Jan 2023 11:57:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pHSn8-0006gz-L4 for bug-gnu-emacs@gnu.org; Mon, 16 Jan 2023 11:57:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pHSn8-00071F-E7 for bug-gnu-emacs@gnu.org; Mon, 16 Jan 2023 11:57:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 16 Jan 2023 16:57:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60859 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 60859-submit@debbugs.gnu.org id=B60859.167388819726929 (code B ref 60859); Mon, 16 Jan 2023 16:57:02 +0000 Original-Received: (at 60859) by debbugs.gnu.org; 16 Jan 2023 16:56:37 +0000 Original-Received: from localhost ([127.0.0.1]:34540 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pHSmj-00070H-5L for submit@debbugs.gnu.org; Mon, 16 Jan 2023 11:56:37 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58718) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pHSmh-000703-84 for 60859@debbugs.gnu.org; Mon, 16 Jan 2023 11:56:36 -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 1pHSmb-0006YR-S9; Mon, 16 Jan 2023 11:56:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=vMCEA8cDJ0LLehdbfgj6oKqiNhy1uWJk2Fb/FG6KXhc=; b=amrXzI4NSMFb 9edpwbmq2Ixsvlil9s7tnglZaNwvz1DnNdFSd/D/a9Dw0z/SLOWyVKcLd3AZbCj84iDoXQT9PUeyY kXbQdc68vXqJqlc0LGiKFeXCoTJQC9ijckSS31cKK2FfwBrEwSAbUeWYUu3+It1aln71yj3VaY70q 9WoisGFtTt9EcT/zOddWkKuzKMkOuhov1xxnjAKhp/S3EfcW2ZCGCEQ/jt/kD/DgLTf2r1HjxPKZT jhkh/WdF1QkstikbHbe6ZlpvZ34X16IBvyuk1yDNmxbfdLBTjXLSVRqwO5XuQNwdxawmrKX9iOYAZ +V8LYLcYjeuE1dLdNfZJBg==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pHSmb-0005IX-0z; Mon, 16 Jan 2023 11:56:29 -0500 In-Reply-To: <87o7qyo3nc.fsf@panoramix.zarniwoop.org> (message from Panagiotis Koutsourakis on Mon, 16 Jan 2023 18:17:11 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:253506 Archived-At: > From: Panagiotis Koutsourakis > Cc: 60859@debbugs.gnu.org > Date: Mon, 16 Jan 2023 18:17:11 +0200 > > On Mon, Jan 16 2023, Eli Zaretskii wrote: > > > I'm not sure we want to stop talking about 'kbd' in the manual. How > > about just adding the 'keymap-global-set' alternative without removing > > 'kbd'? > > > The reasoning behind the submitted patch is twofold: > > > Firstly, in the current wording the description is inconsistent with the > example: "The simplest way is to use @code{kbd} function..." but then in > the example `kbd' is not used at all. > > > Secondly, similar changes happened in the elisp reference manual between > emacs 28 and 29: Compare section 23.15 in emacs 28 with section 23.16 in > emacs 29 (both titled "Commands for Binding Keys"). Moreover, section > 23.13 of the same manual in emacs 29 documents the legacy ways to bind > keys and explicitly says that they should not be used in new code. > > > Having said all that, I have no problem to rewrite it keeping `kbd' both > in text and in a code example, and maybe adding some links to the > relevant sections of the elisp reference. Let me know how I should > proceed. I prefer to keep the description of 'kbd' in the manual. We can (and probably should) reword the text if we are going to the 'keymap-global-set' alternative, and we should probably describe the latter first. > >> I think that this change qualifies as "small", but let me know if you > >> think I need to assign copyright. > > > > You don't need for this change, but if you intend to contribute to > > Emacs in the future, I recommend to start your legal paperwork now, so > > that we will have it ready when you submit your next contribution. > > > > If you agree, I will send you the form to fill. > > > Sure, that's fine with me. Is this form different than the one mentioned > in the CONTRIBUTE file in the source tree? It isn't, but then you don't need to go fetch it. Attached, with the instructions. Thanks. ---------------------------------------------------------------------- Please email the following information to assign@gnu.org, and we will send you the assignment form for your past and future changes. Please use your full legal name (in ASCII characters) as the subject line of the message. ---------------------------------------------------------------------- REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES [What is the name of the program or package you're contributing to?] [Did you copy any files or text written by someone else in these changes? Even if that material is free software, we need to know about it.] [Do you have an employer who might have a basis to claim to own your changes? Do you attend a school which might make such a claim?] [For the copyright registration, what country are you a citizen of?] [What year were you born?] [Please write your email address here.] [Please write your postal address here.] [Which files have you changed so far, and which new files have you written so far?]