From unknown Sun Jun 15 09:02:14 2025 X-Loop: help-debbugs@gnu.org Subject: bug#52821: Should "(elisp) Keymaps" describe key sequences first? Resent-From: Stefan Kangas Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 27 Dec 2021 15:25:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 52821 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: 52821@debbugs.gnu.org X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Received: via spool by submit@debbugs.gnu.org id=B.164061867116861 (code B ref -1); Mon, 27 Dec 2021 15:25:02 +0000 Received: (at submit) by debbugs.gnu.org; 27 Dec 2021 15:24:31 +0000 Received: from localhost ([127.0.0.1]:43965 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n1rrS-0004Ns-Ul for submit@debbugs.gnu.org; Mon, 27 Dec 2021 10:24:31 -0500 Received: from lists.gnu.org ([209.51.188.17]:53572) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n1rrP-0004NW-0Y for submit@debbugs.gnu.org; Mon, 27 Dec 2021 10:24:27 -0500 Received: from eggs.gnu.org ([209.51.188.92]:44658) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n1rrO-0000WE-RT for bug-gnu-emacs@gnu.org; Mon, 27 Dec 2021 10:24:26 -0500 Received: from mail-pg1-f179.google.com ([209.85.215.179]:45015) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n1rrL-000591-Qk for bug-gnu-emacs@gnu.org; Mon, 27 Dec 2021 10:24:26 -0500 Received: by mail-pg1-f179.google.com with SMTP id m15so13742496pgu.11 for ; Mon, 27 Dec 2021 07:24:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=BRAXARY3p/U97fjdLmxoUO5vhcbEvks/j+AjoNSxj7g=; b=lyff7rHn5Zt0cyaNQBZPrrcuw74fzZ+2HhcJZrAaUjp1zlrRVepFrYnqhX8CaUGJ+Z Dp9lLNWg82EPTsMCuBpLTaPynADC4rtvMw0Xq2mfk5FrqeLwm3olVAP9CUgl7I17+i9X 1n6EJ1tY04LKhiZGEHqH7bKUy8hRmwNa2oBrsdrnbhcgzPNkBeW+YQU8x/AWR3vD3HW0 D/LfjuZY72TGCJcmDbhgBiQ6YZ5VS/H88655zPpWugRTfTVImm+PZBE7M7QOWPjJzB9y 5EAEhfJCD51zNgc03gwhN00JRWy/WXFzc0eihOEJ+GOTItCTFEbBsAHNM4OJxJ4xJuV+ /sEw== X-Gm-Message-State: AOAM53105WSna2vDFXO1qt9HlNniG1N33ySkktdxAKNfd8A6N55yyty2 JtKEqOhAvSUd1uzsowCms0sLZV/hD+kV6MC9A471NZKP X-Google-Smtp-Source: ABdhPJxMND4ETzpXKJpSGvaMso7rqBeR8G23AUOw67NXUDhXMoiTrrEocus5S86m+ujElcWosfbKdfVXPhIbF+NAbXc= X-Received: by 2002:a63:4b42:: with SMTP id k2mr15796258pgl.591.1640618662528; Mon, 27 Dec 2021 07:24:22 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Mon, 27 Dec 2021 07:24:22 -0800 From: Stefan Kangas MIME-Version: 1.0 Date: Mon, 27 Dec 2021 07:24:22 -0800 Message-ID: Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=209.85.215.179; envelope-from=stefankangas@gmail.com; helo=mail-pg1-f179.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Spam-Score: -0.8 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.8 (-) Now that we promote the new keymap-* functions, does it really make sense to start the section (info "(elisp) Keymaps") with a description of key sequences? This seems to now be considered more of an internal detail, and the thing that should be exposed to (new) ELisp code is rather the new key description format accepted by `key-valid-p'. I'm thinking it should be moved further down, perhaps in a section next to this one: * Low-Level Key Binding:: Legacy key syntax description. There is a good description on the "new" key format in (info "(elisp) Changing Key Bindings"). Perhaps it should be moved up instead? From unknown Sun Jun 15 09:02:14 2025 X-Loop: help-debbugs@gnu.org Subject: bug#52821: Should "(elisp) Keymaps" describe key sequences first? Resent-From: Richard Stallman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 28 Dec 2021 04:21:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 52821 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Stefan Kangas Cc: 52821@debbugs.gnu.org Reply-To: rms@gnu.org Received: via spool by 52821-submit@debbugs.gnu.org id=B52821.164066524511235 (code B ref 52821); Tue, 28 Dec 2021 04:21:01 +0000 Received: (at 52821) by debbugs.gnu.org; 28 Dec 2021 04:20:45 +0000 Received: from localhost ([127.0.0.1]:44849 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n23yf-0002v8-91 for submit@debbugs.gnu.org; Mon, 27 Dec 2021 23:20:45 -0500 Received: from eggs.gnu.org ([209.51.188.92]:41880) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n23ya-0002ut-8t for 52821@debbugs.gnu.org; Mon, 27 Dec 2021 23:20:43 -0500 Received: from [2001:470:142:3::e] (port=53506 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n23yT-0002C4-OC; Mon, 27 Dec 2021 23:20:34 -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=tfCahPm/vJtyyq8NQDMUuc4pepkIC+6W3yIZu1wmwwk=; b=dgQrCdfQ1wLL Xa1P2oX1hmJxGBBzsGSTQ4ozwBmpi9VRjnJerwxarCPMsT4Fz4V+N5RMUBLLsGg/M1kbc4V/0/Hps nacnDueWxXN3y+49610EvMABoyUnACFk6AEEJ1zN9pZ3fyHqDwX8pKr8Sx0jUP3Eom+vc0M+U1ZRb qJrsispMasqh0Z5pIu1NTVA9nttj9LUTb8/l5o2GAXvYXX7mLVQnZrUhI6SQ3RnJWH/aWsLVA3617 ZLd9nKWQBCASL2Zpg7fF2sRqwjDPtrNw/TTuSN1Q9/VmrdxquUuRgcK/xHNUjcKisFhBQ7GuqdPS4 VmIsSB+M1sdDueqQ4/PxDw==; Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1n23yT-0007OD-La; Mon, 27 Dec 2021 23:20:33 -0500 Content-Type: text/plain; charset=Utf-8 From: Richard Stallman In-Reply-To: (message from Stefan Kangas on Mon, 27 Dec 2021 07:24:22 -0800) References: Message-Id: Date: Mon, 27 Dec 2021 23:20:33 -0500 X-Spam-Score: -2.3 (--) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) [[[ 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. ]]] > Now that we promote the new keymap-* functions, does it really make > sense to start the section (info "(elisp) Keymaps") with a description > of key sequences? > This seems to now be considered more of an internal detail, A key sequence is a Lisp object, and it's not internal -- quite a few programs operate on them. The description in that node is confused between describing the Lisp object itself and describing its printed representation. Perhaps this node should describe the Lisp object format and the issue of printing and inputting them should be elsewhere. -- 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) From unknown Sun Jun 15 09:02:14 2025 X-Loop: help-debbugs@gnu.org Subject: bug#52821: Should "(elisp) Keymaps" describe key sequences first? Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 29 Dec 2021 16:03:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 52821 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: To: Stefan Kangas Cc: 52821@debbugs.gnu.org Received: via spool by 52821-submit@debbugs.gnu.org id=B52821.164079377221038 (code B ref 52821); Wed, 29 Dec 2021 16:03:01 +0000 Received: (at 52821) by debbugs.gnu.org; 29 Dec 2021 16:02:52 +0000 Received: from localhost ([127.0.0.1]:50038 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n2bPg-0005TG-1A for submit@debbugs.gnu.org; Wed, 29 Dec 2021 11:02:52 -0500 Received: from quimby.gnus.org ([95.216.78.240]:43244) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n2bPV-0005J3-6K for 52821@debbugs.gnu.org; Wed, 29 Dec 2021 11:02:51 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Ta9wG+slznui8tJHsp91uoa+cMsMMTuE49shi1x88LQ=; b=nXY2o4PW7XG9XXym92Xn+g+B1h IW079S3nlbAGkUL85Ad9kEDr1MxZD8S0qnet/ePjFCl70G/ES7dsstc4h5866m4uLsrjHXnFoRCY8 0JMobnorTOTa5BWRhz4p3KoqPQbTA7STwe0u1VmFT+kWRdr6bnPw5enMVHAPY7iALCPA=; Received: from [84.212.220.105] (helo=xo) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n2bPM-0007Qt-Mz; Wed, 29 Dec 2021 17:02:35 +0100 From: Lars Ingebrigtsen References: X-Now-Playing: Four Tet's _Rounds_: "Unspoken" Date: Wed, 29 Dec 2021 17:02:32 +0100 In-Reply-To: (Stefan Kangas's message of "Mon, 27 Dec 2021 07:24:22 -0800") Message-ID: <875yr75rhj.fsf@gnus.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Report: Spam detection software, running on the system "quimby.gnus.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Stefan Kangas writes: > Now that we promote the new keymap-* functions, does it really make > sense to start the section (info "(elisp) Keymaps") with a description > of key sequences? > > This seems to now be considered m [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Spam-Score: 0.0 (/) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) Stefan Kangas writes: > Now that we promote the new keymap-* functions, does it really make > sense to start the section (info "(elisp) Keymaps") with a description > of key sequences? > > This seems to now be considered more of an internal detail, and the > thing that should be exposed to (new) ELisp code is rather the new key > description format accepted by `key-valid-p'. > > I'm thinking it should be moved further down, perhaps in a section next > to this one: > > * Low-Level Key Binding:: Legacy key syntax description. Yes, sounds good to me. > There is a good description on the "new" key format in > (info "(elisp) Changing Key Bindings"). Perhaps it should > be moved up instead? Yup. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no From unknown Sun Jun 15 09:02:14 2025 MIME-Version: 1.0 X-Mailer: MIME-tools 5.505 (Entity 5.505) X-Loop: help-debbugs@gnu.org From: help-debbugs@gnu.org (GNU bug Tracking System) To: Stefan Kangas Subject: bug#52821: closed (Re: bug#52821: Should "(elisp) Keymaps" describe key sequences first?) Message-ID: References: X-Gnu-PR-Message: they-closed 52821 X-Gnu-PR-Package: emacs Reply-To: 52821@debbugs.gnu.org Date: Sat, 01 Mar 2025 05:38:02 +0000 Content-Type: multipart/mixed; boundary="----------=_1740807482-18756-1" This is a multi-part message in MIME format... ------------=_1740807482-18756-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Your bug report #52821: Should "(elisp) Keymaps" describe key sequences first? which was filed against the emacs package, has been closed. The explanation is attached below, along with your original report. If you require more details, please reply to 52821@debbugs.gnu.org. --=20 52821: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D52821 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems ------------=_1740807482-18756-1 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at 52821-done) by debbugs.gnu.org; 1 Mar 2025 05:37:45 +0000 Received: from localhost ([127.0.0.1]:58637 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1toFXk-0004rK-B7 for submit@debbugs.gnu.org; Sat, 01 Mar 2025 00:37:45 -0500 Received: from mail-ed1-x533.google.com ([2a00:1450:4864:20::533]:46115) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1toFXh-0004qU-II for 52821-done@debbugs.gnu.org; Sat, 01 Mar 2025 00:37:42 -0500 Received: by mail-ed1-x533.google.com with SMTP id 4fb4d7f45d1cf-5e4b410e48bso4220031a12.0 for <52821-done@debbugs.gnu.org>; Fri, 28 Feb 2025 21:37:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1740807455; x=1741412255; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:from:to:cc:subject:date:message-id:reply-to; bh=iUHgTMhBXfriC67xBtZ8RVkG/qJ7DC5m1uzgpaOjxGQ=; b=ILP7XD8muh25D0uvzLCPWLdlwb4e4ymMD1Klwkq4YQUfLOQVzCVXmJbDHKHnse2m0W 6n8w3Y5AI5kVCLRtoMYq90tDjfgE7TF50H0Dx20TTc6epIA0wPBcpHTjPusoRX8jW2zO UVpqLDBYAvVzDFlDYreWLrJN43yAFoZX3bhkWiQr5ykvRCanUOhGmsV1qkrjIHdq/E5m GHwHAI386YeMGSvnZwqLpPCAUQfhioq6+uoRQL3XiIpjyI0Pc7X0X6DtQa3VlZH7TOLQ KyaOFjR1weGEOyzU6yjfW6kx44EoABTHiZluufDx13K+aNLJSDnsFJQrCTvvIbNAM+MB c20A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740807455; x=1741412255; h=cc:to:subject:message-id:date:mime-version:references:in-reply-to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=iUHgTMhBXfriC67xBtZ8RVkG/qJ7DC5m1uzgpaOjxGQ=; b=KQRzw30GbvFAIacZUeXCM5rMKdQwiSLW5l0SBzp4rYHKnMncmps5Zd1iXXt7TCLx3Z W+BMAMWJqz9GnZR2n5Is0Ce8q9FVOxpZdE8tyR4hPcXSk6C+BEC61hHduDoTDsskgu8P lCjYGatX1eDByZyXO+fPnYLm88fSuHbmR/bxac768UxIoWRfujKLzbtBSiwXDvU/6Wl+ 5cHYF2ZZscVpCnm8KWej3p6ZBtW3Yy6sPDqHo8bkIPnChhOTKfAHpyL24tCSGpinS2cE uJpVm10Ssb/92mGHmHaTQYZUQl/PmfL1Z8iF5lDOOl7IyT2NevTDPjE9wiol4mKr/YKW XVMg== X-Gm-Message-State: AOJu0YwwOiheDKXxECX/TuN8m+vSqobda7NSGsMDtyp5AUGhpTHzlrln 55h5kyel5x2TeO7kX6hCPv7Rle+qPMDjJmXeopiu94di5xatgvGTuCdc+F9KXosBLd+HMVSj5Ci sWhF7mNvdteBydOyYTHXK4ZJbx1Q= X-Gm-Gg: ASbGnctLrgwM6orPUF1JZh1uN4U0Uvdx9uCzL5blu4+xQExg8HIec3IMso1XQBSPwm2 HjTN3WUoTJcK5nbFEZleZrL9XryPc+Kb3JycpKuHyyYHRGUcvy9ensU6GVpxpL09PsdpVpvXsYi 8wMJheVr80n0g52sSIAE7gUe4/5w== X-Google-Smtp-Source: AGHT+IEfPFEqT8OI/Ix6qGnxw0wUR+SGT25XycXbt2uCnC0G2Vm+faJszSv2C6recHvp4975ssX9apnzUKJMHJWTVfM= X-Received: by 2002:a50:cc0c:0:b0:5e4:d75a:573e with SMTP id 4fb4d7f45d1cf-5e4d75a57fcmr4140612a12.32.1740807454951; Fri, 28 Feb 2025 21:37:34 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Fri, 28 Feb 2025 21:37:34 -0800 From: Stefan Kangas In-Reply-To: <875yr75rhj.fsf@gnus.org> References: <875yr75rhj.fsf@gnus.org> MIME-Version: 1.0 Date: Fri, 28 Feb 2025 21:37:34 -0800 X-Gm-Features: AQ5f1JoRt4tQlSEmORMv-klKz8uBUJ54__LoXYTW6VYSEKtv2-3B5hF2bFvctpk Message-ID: Subject: Re: bug#52821: Should "(elisp) Keymaps" describe key sequences first? To: Lars Ingebrigtsen Content-Type: text/plain; charset="UTF-8" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 52821-done Cc: 52821-done@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) Version: 30.2 Lars Ingebrigtsen writes: > Stefan Kangas writes: > >> Now that we promote the new keymap-* functions, does it really make >> sense to start the section (info "(elisp) Keymaps") with a description >> of key sequences? >> >> This seems to now be considered more of an internal detail, and the >> thing that should be exposed to (new) ELisp code is rather the new key >> description format accepted by `key-valid-p'. >> >> I'm thinking it should be moved further down, perhaps in a section next >> to this one: >> >> * Low-Level Key Binding:: Legacy key syntax description. > > Yes, sounds good to me. > >> There is a good description on the "new" key format in >> (info "(elisp) Changing Key Bindings"). Perhaps it should >> be moved up instead? > > Yup. Now done on emacs-30. I'm therefore closing this bug report. ------------=_1740807482-18756-1 Content-Type: message/rfc822 Content-Disposition: inline Content-Transfer-Encoding: 7bit Received: (at submit) by debbugs.gnu.org; 27 Dec 2021 15:24:31 +0000 Received: from localhost ([127.0.0.1]:43965 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n1rrS-0004Ns-Ul for submit@debbugs.gnu.org; Mon, 27 Dec 2021 10:24:31 -0500 Received: from lists.gnu.org ([209.51.188.17]:53572) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n1rrP-0004NW-0Y for submit@debbugs.gnu.org; Mon, 27 Dec 2021 10:24:27 -0500 Received: from eggs.gnu.org ([209.51.188.92]:44658) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n1rrO-0000WE-RT for bug-gnu-emacs@gnu.org; Mon, 27 Dec 2021 10:24:26 -0500 Received: from mail-pg1-f179.google.com ([209.85.215.179]:45015) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n1rrL-000591-Qk for bug-gnu-emacs@gnu.org; Mon, 27 Dec 2021 10:24:26 -0500 Received: by mail-pg1-f179.google.com with SMTP id m15so13742496pgu.11 for ; Mon, 27 Dec 2021 07:24:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=BRAXARY3p/U97fjdLmxoUO5vhcbEvks/j+AjoNSxj7g=; b=lyff7rHn5Zt0cyaNQBZPrrcuw74fzZ+2HhcJZrAaUjp1zlrRVepFrYnqhX8CaUGJ+Z Dp9lLNWg82EPTsMCuBpLTaPynADC4rtvMw0Xq2mfk5FrqeLwm3olVAP9CUgl7I17+i9X 1n6EJ1tY04LKhiZGEHqH7bKUy8hRmwNa2oBrsdrnbhcgzPNkBeW+YQU8x/AWR3vD3HW0 D/LfjuZY72TGCJcmDbhgBiQ6YZ5VS/H88655zPpWugRTfTVImm+PZBE7M7QOWPjJzB9y 5EAEhfJCD51zNgc03gwhN00JRWy/WXFzc0eihOEJ+GOTItCTFEbBsAHNM4OJxJ4xJuV+ /sEw== X-Gm-Message-State: AOAM53105WSna2vDFXO1qt9HlNniG1N33ySkktdxAKNfd8A6N55yyty2 JtKEqOhAvSUd1uzsowCms0sLZV/hD+kV6MC9A471NZKP X-Google-Smtp-Source: ABdhPJxMND4ETzpXKJpSGvaMso7rqBeR8G23AUOw67NXUDhXMoiTrrEocus5S86m+ujElcWosfbKdfVXPhIbF+NAbXc= X-Received: by 2002:a63:4b42:: with SMTP id k2mr15796258pgl.591.1640618662528; Mon, 27 Dec 2021 07:24:22 -0800 (PST) Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Mon, 27 Dec 2021 07:24:22 -0800 From: Stefan Kangas MIME-Version: 1.0 Date: Mon, 27 Dec 2021 07:24:22 -0800 Message-ID: Subject: Should "(elisp) Keymaps" describe key sequences first? To: bug-gnu-emacs@gnu.org Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=209.85.215.179; envelope-from=stefankangas@gmail.com; helo=mail-pg1-f179.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.248, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-Spam-Score: -0.8 (/) X-Debbugs-Envelope-To: submit X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.8 (-) Now that we promote the new keymap-* functions, does it really make sense to start the section (info "(elisp) Keymaps") with a description of key sequences? This seems to now be considered more of an internal detail, and the thing that should be exposed to (new) ELisp code is rather the new key description format accepted by `key-valid-p'. I'm thinking it should be moved further down, perhaps in a section next to this one: * Low-Level Key Binding:: Legacy key syntax description. There is a good description on the "new" key format in (info "(elisp) Changing Key Bindings"). Perhaps it should be moved up instead? ------------=_1740807482-18756-1--