From: Panagiotis Koutsourakis <kutsurak@slartibartfast.net>
To: 60859@debbugs.gnu.org
Subject: bug#60859: [PATCH] Remove reference to the kbd function from documentation
Date: Mon, 16 Jan 2023 13:15:22 +0200 [thread overview]
Message-ID: <87pmbeivcl.fsf@panoramix.zarniwoop.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: 0001-Remove-reference-to-the-kbd-function-from-documentat.patch --]
[-- Type: text/x-patch, Size: 1249 bytes --]
From c0de146a194603a463147a819d96c9f7d0eb61e3 Mon Sep 17 00:00:00 2001
From: Panagiotis Koutsourakis <kutsurak@slartibartfast.net>
Date: Mon, 16 Jan 2023 11:49:05 +0200
Subject: [PATCH] Remove reference to the kbd function from documentation
---
doc/emacs/custom.texi | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/doc/emacs/custom.texi b/doc/emacs/custom.texi
index 91df15a21d7..650a96f14b1 100644
--- a/doc/emacs/custom.texi
+++ b/doc/emacs/custom.texi
@@ -1887,12 +1887,8 @@ Init Rebinding
you can specify them in your initialization file by writing Lisp code.
@xref{Init File}, for a description of the initialization file.
-@findex kbd
- There are several ways to write a key binding using Lisp. The
-simplest is to use the @code{kbd} function, which converts a textual
-representation of a key sequence---similar to how we have written key
-sequences in this manual---into a form that can be passed as an
-argument to @code{keymap-global-set}. For example, here's how to bind
+ The simplest way to write a key binding using Lisp is to use the
+@code{keymap-global-set} function. For example, here's how to bind
@kbd{C-z} to the @code{shell} command (@pxref{Interactive Shell}):
@example
--
2.39.0
[-- Attachment #2: Type: text/plain, Size: 392 bytes --]
Hi emacs devs,
I am attaching a patch to the manual for emacs 29 that removes from the
text a reference to the `kbd' function when creating a key binding in
Lisp. The example that follows is correct (i.e. it works for me), but
the explanation seems outdated.
I think that this change qualifies as "small", but let me know if you
think I need to assign copyright.
--
Best regards,
Panos.
next reply other threads:[~2023-01-16 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 11:15 Panagiotis Koutsourakis [this message]
2023-01-16 14:47 ` bug#60859: [PATCH] Remove reference to the kbd function from documentation Eli Zaretskii
2023-01-16 16:17 ` Panagiotis Koutsourakis
2023-01-16 16:56 ` Eli Zaretskii
2023-01-17 14:20 ` Panagiotis Koutsourakis
2023-01-17 14:56 ` Robert Pluim
2023-01-17 16:09 ` Panagiotis Koutsourakis
2023-01-17 17:16 ` Robert Pluim
2023-01-17 17:32 ` Eli Zaretskii
2023-01-17 19:40 ` Panagiotis Koutsourakis
2023-01-21 7:52 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmbeivcl.fsf@panoramix.zarniwoop.org \
--to=kutsurak@slartibartfast.net \
--cc=60859@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).