From: john muhl <jm@pub.pink>
To: 72093@debbugs.gnu.org
Subject: bug#72093: [PATCH] ; Fix typos in 'which-key-mode'
Date: Sat, 13 Jul 2024 10:35:18 -0500 [thread overview]
Message-ID: <87y165pao9.fsf@pub.pink> (raw)
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
Tags: patch
In GNU Emacs 31.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version
3.24.42, cairo version 1.18.0) of 2024-07-07 built on thelio
Repository revision: d98c31ae2ca83a1ba8615401aa6d19d80c521b48
Repository branch: main
System Description: Fedora Linux 40 (Workstation Edition)
Configured using:
'configure -C --with-pgtk --prefix=/home/jm/.local'
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-typos-in-which-key-mode.patch --]
[-- Type: text/patch, Size: 2184 bytes --]
From 6a541bf59f43785e3657b86133ca55945152e125 Mon Sep 17 00:00:00 2001
From: john muhl <jm@pub.pink>
Date: Wed, 10 Jul 2024 17:13:58 -0500
Subject: [PATCH] ; Fix typos in 'which-key-mode'
* lisp/which-key.el (which-key-preserve-window-configuration):
Correct spelling of "taken".
(which-key--create-pages): Correct spelling of "widths".
(which-key--start-paging-timer): Correct spelling of "secondary".
---
lisp/which-key.el | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lisp/which-key.el b/lisp/which-key.el
index 677a84b328d..37b42a009f7 100644
--- a/lisp/which-key.el
+++ b/lisp/which-key.el
@@ -444,7 +444,7 @@ which-key-preserve-window-configuration
If non-nil, save window configuration before which-key buffer is
shown and restore it after which-key buffer is hidden. It
prevents which-key from changing window position of visible
-buffers. Only takken into account when popup type is
+buffers. Only taken into account when popup type is
side-window."
:type 'boolean
:package-version "1.0" :version "30.1")
@@ -2113,7 +2113,7 @@ which-key--create-pages-1
(defun which-key--create-pages (keys &optional prefix-keys prefix-title)
"Create page strings using `which-key--list-to-pages'.
Will try to find the best number of rows and columns using the
-given dimensions and the length and wdiths of KEYS. SEL-WIN-WIDTH
+given dimensions and the length and widths of KEYS. SEL-WIN-WIDTH
is the width of the live window."
(let* ((max-dims (which-key--popup-max-dimensions))
(max-lines (car max-dims))
@@ -2825,7 +2825,7 @@ which-key--start-paging-timer
(funcall which-key-this-command-keys-function)))))
(cancel-timer which-key--paging-timer)
(if which-key-idle-secondary-delay
- ;; we haven't executed a command yet so the secandary
+ ;; we haven't executed a command yet so the secondary
;; timer is more relevant here
(which-key--start-timer which-key-idle-secondary-delay t)
(which-key--start-timer)))))))
--
2.45.2
next reply other threads:[~2024-07-13 15:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 15:35 john muhl [this message]
2024-07-13 15:51 ` bug#72093: [PATCH] ; Fix typos in 'which-key-mode' Eli Zaretskii
2024-07-13 15:55 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87y165pao9.fsf@pub.pink \
--to=jm@pub.pink \
--cc=72093@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).