all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Voss via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 65328@debbugs.gnu.org
Subject: bug#65328: Patch to fix typos in lisp/keymap.el
Date: Wed, 16 Aug 2023 02:01:57 +0200	[thread overview]
Message-ID: <87sf8jetqo.fsf@thomasvoss.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 169 bytes --]

Hi!  I noticed a few typos in the documentation comments for
‘keymap-global-set’ and ‘keymap-local-set’, so here’s a quick patch to
fix them.

— Thomas

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch --]
[-- Type: text/x-patch, Size: 1284 bytes --]

From 13683ba6879027f1524a4822b235c8a4ded6859f Mon Sep 17 00:00:00 2001
From: Thomas Voss <mail@thomasvoss.com>
Date: Wed, 16 Aug 2023 01:58:03 +0200
Subject: [PATCH] ; Fix typos in lisp/keymap.el

Copyright-paper-exempt: yes
---
 lisp/keymap.el | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/lisp/keymap.el b/lisp/keymap.el
index cd06b830e0a..017b2d6ead0 100644
--- a/lisp/keymap.el
+++ b/lisp/keymap.el
@@ -78,7 +78,7 @@ called from Lisp, COMMAND can be anything that `keymap-set' accepts
 as its DEFINITION argument.
 
 If COMMAND is a string (which can only happen when this function is
-callled from Lisp), it must satisfy `key-valid-p'.
+called from Lisp), it must satisfy `key-valid-p'.
 
 Note that if KEY has a local binding in the current buffer,
 that local binding will continue to shadow any global binding
@@ -102,7 +102,7 @@ called from Lisp, COMMAND can be anything that `keymap-set' accepts
 as its DEFINITION argument.
 
 If COMMAND is a string (which can only happen when this function is
-callled from Lisp), it must satisfy `key-valid-p'.
+called from Lisp), it must satisfy `key-valid-p'.
 
 The binding goes in the current buffer's local keymap, which in most
 cases is shared with all other buffers in the same major mode."
-- 
2.41.0


                 reply	other threads:[~2023-08-16  0:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sf8jetqo.fsf@thomasvoss.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=65328@debbugs.gnu.org \
    --cc=mail@thomasvoss.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.